| /linux/Documentation/fb/ |
| H A D | cirrusfb.rst | 60 * Bug fixes.
69 * Compile fixes related to new 2.3.x IORESOURCE_IO[PORT] symbol changes.
76 * Casting fixes.
78 * Bug fixes.
|
| /linux/Documentation/admin-guide/cifs/ |
| H A D | authors.rst | 42 - 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)
|
| H A D | changes.rst | 6 information about fixes/improvements to CIFS/SMB2/SMB3 support (changes
|
| /linux/drivers/net/dsa/mv88e6xxx/ |
| H A D | pcs-639x.c | 679 } fixes[] = { in mv88e6393x_erratum_5_2() local
691 for (i = 0; i < ARRAY_SIZE(fixes); ++i) { in mv88e6393x_erratum_5_2()
692 err = mdiodev_c45_modify(&mpcs->mdio, fixes[i].dev, in mv88e6393x_erratum_5_2()
693 fixes[i].reg, fixes[i].mask, in mv88e6393x_erratum_5_2()
694 fixes[i].val); in mv88e6393x_erratum_5_2()
|
| /linux/Documentation/process/ |
| H A D | maintainer-kvm-x86.rst | 27 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``
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).
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
228 If a change fixes a KVM/kernel bug, add a Fixes: tag even if the change doesn't
229 need to be backported to stable kernels, and even if the change fixes a bug in
296 Except for "obvious" found-by-inspection bugs, fixes must be accompanied by a
[all …]
|
| H A D | cve.rst | 48 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 D | maintainer-netdev.rst | 13 - 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.
275 Security fixes
318 Specifically for fixes both code change and related test should go into
[all …]
|
| H A D | handling-regressions.rst | 43 #. 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
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
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
258 periods mentioned above by reviewing regression fixes in a timely manner.
261 of regression fixes. Thus evaluate if skipping linux-next is an option for
[all …]
|
| H A D | security-bugs.rst | 52 Although our preference is to release fixes for publicly undisclosed bugs
107 reports or fixes, as this can needlessly complicate the process and may
|
| /linux/drivers/gpib/ |
| H A D | TODO | 2 - checkpatch.pl fixes
|
| /linux/fs/affs/ |
| H A D | Changes | 40 - 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/ |
| H A D | CREDITS | 152 D: VFS fixes (new notify_change in particular)
275 D: Various parport/ppdev hacks and fixes
493 D: Various fixes (mostly networking)
773 D: Various build fixes and kernel documentation.
795 D: Various security things, bug fixes, and documentation.
1148 D: verify_area stuff, generic SCSI fixes
1168 D: Various kernel hacks, fixes, and cleanups.
1225 D: Mitsumi LU005 tests and fixes
1226 D: port and fixes of cs46xx sounddriver
1247 D: romfs, various (mostly networking) fixes
[all …]
|
| /linux/fs/notify/inotify/ |
| H A D | Kconfig | 11 Inotify fixes numerous shortcomings in dnotify and introduces several
|
| /linux/drivers/hid/bpf/progs/ |
| H A D | README | 3 This directory contains various fixes for devices. They add new features or
13 The main reasons for these fixes to be here is to have a central place to
|
| /linux/Documentation/scsi/ |
| H A D | ChangeLog.sym53c8xx_2 | 75 has been allocated. This fixes a panic if attach failed.
80 - A couple of comments fixes.
100 - A couple of tiny fixes ...
|
| H A D | ChangeLog.ncr53c8xx | 161 - 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
|
| /linux/Documentation/livepatch/ |
| H A D | cumulative-patches.rst | 38 removing various fixes or features.
88 fixes/features are added/removed and what special actions are necessary
|
| /linux/Documentation/doc-guide/ |
| H A D | contributing.rst | 51 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/Documentation/i2c/busses/ |
| H A D | i2c-sis630.rst | 61 - bug fixes
|
| /linux/Documentation/arch/x86/ |
| H A D | iommu.rst | 69 If this fixes anything, please ensure you file a bug reporting the problem.
86 this fixes anything, please ensure you file a bug reporting the problem.
|
| /linux/Documentation/driver-api/acpi/ |
| H A D | linuxized-acpica.rst | 207 2. Manual modifications - Any manual modification (eg. coding style fixes)
221 avoid breaking Linux bisection, fixes are applied directly to the
227 fixes or stable-candidate material, so they are applied in advance with
|
| /linux/drivers/mmc/host/ |
| H A D | sdhci-pci.h | 183 const struct sdhci_pci_fixes *fixes; member
|
| /linux/Documentation/devicetree/bindings/sifive/ |
| H A D | sifive-blocks-ip-versioning.txt | 31 integration-specific bug fixes or workarounds are needed, the kernel
|
| /linux/arch/arm/mach-sa1100/ |
| H A D | sleep.S | 54 @ fixes resume problem on high speed SA1110
|
| /linux/Documentation/translations/ |
| H A D | index.rst | 48 translations, updates, fixes).
|