Home
last modified time | relevance | path

Searched full:fixes (Results 1 – 25 of 523) sorted by relevance

12345678910>>...21

/linux/Documentation/process/
H A Dmaintainer-kvm-x86.rst27 Generally speaking, fixes for the current cycle are applied directly to the
30 through the KVM x86 tree, it will be applied to the ``fixes`` branch before
45 All topic branches, except for ``next`` and ``fixes``, are rolled into ``next``
51 Fixes that target the current release, a.k.a. mainline, are typically applied
61 close around rc5 for new features, and a soft close around rc6 for fixes (for
62 the next release; see above for fixes that target the current release).
67 room for the size of a series, patches that are "cache hot", etc. Fixes,
87 Fixes that target the current release, a.k.a. mainline, should be based on
88 ``git://git.kernel.org/pub/scm/virt/kvm/kvm.git master``. Note, fixes do not
90 rule, but typically only fixes for bugs that are urgent, critical, and/or were
[all …]
H A Dmaintainer-netdev.rst13 - for fixes the ``Fixes:`` tag is required, regardless of the tree
43 features get mainlined after this -- only fixes to the rc1 content are
44 expected. After roughly a week of collecting fixes to the rc1 content,
67 the names, the ``net`` tree is for fixes to existing code already in the
78 ``net`` tree will start accumulating fixes for this pulled content
102 The ``net`` tree continues to collect fixes for the vX.Y content, and is
104 focus for ``net`` is on stabilization and bug fixes.
264 when original change is completely wrong; incremental fixes are preferred.
273 and make sure you include appropriate Fixes tags!
275 Security fixes
[all …]
H A Dcve.rst48 of CVEs for fixes that are already in released kernel trees. If you
117 the sum of many fixes on top of each other. Ideally CVEs will be
118 assigned to all fixes for all issues, but sometimes we will fail to
119 notice fixes, therefore assume that some changes without a CVE assigned
H A Dsubmitting-patches.rst135 In case your patch fixes a bug, use the 'Closes:' tag with a URL referencing
145 If your patch fixes a bug in a specific commit, e.g. you found an issue using
146 ``git bisect``, please use the 'Fixes:' tag with the first 12 characters of
151Fixes: 54a4f0239f2e ("KVM: MMU: make kvm_mmu_zap_page() return the number of pages it actually fre…
159 fixes = Fixes: %h (\"%s\")
163 $ git log -1 --pretty=fixes 54a4f0239f2e
164Fixes: 54a4f0239f2e ("KVM: MMU: make kvm_mmu_zap_page() return the number of pages it actually fre…
173 For example, if your changes include both bug fixes and performance
256 If you have a patch that fixes an exploitable security bug, send that patch
525 Using Reported-by:, Tested-by:, Reviewed-by:, Suggested-by: and Fixes:
[all …]
H A Dstable-kernel-rules.rst18 - It fixes a problem like an oops, a hang, data corruption, a real security
23 As these fixes are not as obvious and have a higher risk of a subtle
30 - No "trivial" fixes without benefit for users (spelling changes, whitespace
122 appropriate versions from Fixes: tags.
134 containing a 'Fixes:' tag) ignore a change::
H A Dsecurity-bugs.rst42 Once a robust fix has been developed, the release process starts. Fixes
45 Although our preference is to release fixes for publicly undisclosed bugs
100 reports or fixes, as this can needlessly complicate the process and may
H A Dhandling-regressions.rst43 #. When submitting fixes for regressions, add "Closes:" tags to the patch
51 #. Try to fix regressions quickly once the culprit has been identified; fixes
113 You don't need to do anything special when submitting fixes for regression, just
127 * Add a "Fixes:" tag to specify the commit causing the regression.
186 * For other regressions, aim to mainline fixes before the hindmost Sunday
191 * It's strongly discouraged to delay mainlining regression fixes till the next
214 fixes. Ideally though such requests should happen in accordance with the
231 "Fixes:" tag alone does not guarantee a backport. Please add the same tag,
245 * In case of urgent regression fixes you might want to ensure prompt
253 to account for the time it takes to get fixes tested, reviewed, and merged by
[all …]
/linux/Documentation/admin-guide/cifs/
H A Dauthors.rst42 - Kazeon team for various fixes especially for 2.4 version.
47 - Jeff Layton (many, many fixes, as well as great work on the cifs Kerberos code)
50 - Aurelien Aptel (for DFS SMB3 work and some key bug fixes)
51 - Ronnie Sahlberg (for SMB3 xattr work, bug fixes, and lots of great work on compounding)
53 - Sachin Prabhu (many bug fixes, including for reconnect, copy offload and security)
/linux/Documentation/driver-api/firmware/
H A Dfirmware-usage-guidelines.rst22 fixes/changes. The firmware files in linux-firmware should be
35 * If a security fix needs lockstep firmware and kernel fixes in order to
40 is fixed. All communications around security fixes should point at
41 both the firmware and kernel fixes. If a security fix requires
/linux/arch/m68k/kernel/
H A Dvectors.c6 * 68040 fixes by Michael Rausch
7 * 68040 fixes by Martin Apel
8 * 68040 fixes and writeback by Richard Zidlicky
9 * 68060 fixes by Roman Hodek
10 * 68060 fixes by Jesper Skov
/linux/Documentation/fb/
H A Dcirrusfb.rst60 * Bug fixes.
69 * Compile fixes related to new 2.3.x IORESOURCE_IO[PORT] symbol changes.
76 * Casting fixes.
78 * Bug fixes.
/linux/
H A DCREDITS148 D: VFS fixes (new notify_change in particular)
271 D: Various parport/ppdev hacks and fixes
485 D: Various fixes (mostly networking)
765 D: Various build fixes and kernel documentation.
787 D: Various security things, bug fixes, and documentation.
1136 D: verify_area stuff, generic SCSI fixes
1156 D: Various kernel hacks, fixes, and cleanups.
1213 D: Mitsumi LU005 tests and fixes
1214 D: port and fixes of cs46xx sounddriver
1235 D: romfs, various (mostly networking) fixes
[all …]
/linux/drivers/video/fbdev/matrox/
H A Dmatroxfb_accel.c13 * Betatesting, fixes, ideas
16 * Betatesting, fixes, ideas, videomodes, videomodes timmings
19 * MTRR stuff, PPC cleanups, betatesting, fixes, ideas
26 * Testing, hardware cursor fixes
29 * Fixes
39 * Fixes, ideas, betatesting
42 * Fixes, enhandcements, ideas, betatesting
62 * CHRP fixes and PReP cleanup
H A Dmatroxfb_Ti3026.c15 * Betatesting, fixes, ideas
18 * Betatesting, fixes, ideas, videomodes, videomodes timmings
21 * MTRR stuff, PPC cleanups, betatesting, fixes, ideas
28 * Testing, hardware cursor fixes
31 * Fixes
41 * Fixes, ideas, betatesting
44 * Fixes, enhandcements, ideas, betatesting
64 * CHRP fixes and PReP cleanup
/linux/Documentation/translations/zh_TW/process/
H A Dsubmitting-patches.rst117 帶有前12個字符SHA-1 ID的“Fixes:”標籤和單行摘要。爲了簡化解析腳本,不要將該
120Fixes: 54a4f0239f2e ("KVM: MMU: make kvm_mmu_zap_page() return the number of pages it actually fre…
127 fixes = Fixes: %h (\"%s\")
131 $ git log -1 --pretty=fixes 54a4f0239f2e
132Fixes: 54a4f0239f2e ("KVM: MMU: make kvm_mmu_zap_page() return the number of pages it actually fre…
438 Fixes: 指示補丁修復了之前提交的一個問題。它可以便於確定錯誤的來源,這有助於
/linux/Documentation/translations/zh_CN/process/
H A Dsubmitting-patches.rst116 带有前12个字符SHA-1 ID的“Fixes:”标签和单行摘要。为了简化解析脚本,不要将该
119Fixes: 54a4f0239f2e ("KVM: MMU: make kvm_mmu_zap_page() return the number of pages it actually fre…
126 fixes = Fixes: %h (\"%s\")
130 $ git log -1 --pretty=fixes 54a4f0239f2e
131Fixes: 54a4f0239f2e ("KVM: MMU: make kvm_mmu_zap_page() return the number of pages it actually fre…
434 Fixes: 指示补丁修复了之前提交的一个问题。它可以便于确定错误的来源,这有助于
/linux/fs/affs/
H A DChanges40 - several bug fixes found with fsx
45 - change to global min macro + warning fixes
51 - locking fixes
66 - locking fixes for link creation/removal.
86 more 2.4 fixes: [Roman Zippel]
/linux/Documentation/filesystems/xfs/
H A Dxfs-maintainer-entry-profile.rst95 - **LTS Maintainer**: Someone who backports and tests bug fixes from
164 - Patchsets implementing bug fixes and further code cleanups should put
165 the bug fixes at the beginning of the series to ease backporting.
169 Bug fixes may be sent at any time, though the release manager may decide to
/linux/drivers/mfd/
H A D88pm80x.c40 * pm800 and pm805. would remove it after HW chip fixes the issue.
104 * remove it after HW chip fixes the issue. in pm80x_init()
121 * would remove it after HW chip fixes the issue. in pm80x_deinit()
/linux/Documentation/scsi/
H A DChangeLog.ncr53c8xx161 - Miscellaneous minor fixes.
224 - Minor spelling fixes in doc files.
289 - Preliminary fixes for Big Endian (sent by Eddie C. Dost).
299 - Some spelling fixes.
307 - Some cleanup, spelling fixes, version checks, documentations
322 This also fixes a bug triggered when disabling tagged command
432 - Some fixes.
449 - Some fixes in order to really support the 53C895, at least with
H A DChangeLog.sym53c8xx_275 has been allocated. This fixes a panic if attach failed.
80 - A couple of comments fixes.
100 - A couple of tiny fixes ...
H A DChangeLog.lpfc160 worker thread. Fixes panic seen with insmod/rmmod testing with
182 * Integrated Christoph Hellwig's patch from 1/30: Some fixes in
333 * rport fixes: fix for rmmod crash
334 * rport fixes: when receiving PRLI's, set node/rport role values
335 * rport fixes: fix for unload and for fabric port deletes
348 * rport fixes: for fport, get maxframe and class support
375 This effort fixes the number of bdes per scsi_buf to 64, makes
453 returning. Fixes some panics in iocb completion code path.
509 * Fixes to lpfc_els_chk_latt().
679 * Bug fixes for some insmod/rmmod crashes, link down crashes and
[all …]
/linux/Documentation/doc-guide/
H A Dcontributing.rst51 maintainer appreciates being copied on fixes for these warnings, the
53 fixes; they should go to the maintainer of the subsystem in question.
133 Other fixes will take longer, especially those relating to structure
165 Typo fixes
203 - Nothing but typo fixes in the history for several years
/linux/drivers/hid/
H A Dhid-speedlink.c4 * Fixes "jumpy" cursor and removes nonexistent keyboard LEDS from
47 /* This fixes the "jumpy" cursor occuring due to invalid events sent in speedlink_event()
/linux/arch/m68k/coldfire/
H A Dentry.S19 * 68060 fixes by Jesper Skov
21 * 5307 fixes by David W. Miller
23 * Bug, speed and maintainability fixes by Philippe De Muyter <phdm@macqel.be>

12345678910>>...21