/linux-4.4.14/Documentation/ |
D | email-clients.txt | 8 end, maintainers use `git am` to apply the patches. 24 Email clients that are used for Linux kernel patches should send the 28 Don't send patches with "format=flowed". This can cause unexpected 35 Emailed patches should be in ASCII or UTF-8 encoding only. 42 Copy-and-paste (or cut-and-paste) usually does not work for patches 47 Don't use PGP/GPG signatures in mail that contains patches. 48 This breaks many scripts that read and apply the patches. 52 and successfully apply it with 'patch' before sending patches to Linux 59 patches for the Linux kernel. These are not meant to be complete 82 Works. Some people use this successfully for patches. [all …]
|
D | applying-patches.txt | 14 In addition to explaining how to apply and revert patches, a brief 16 their specific patches) is also provided. 124 If you don't have any third-party patches applied to your kernel source, but 125 only patches from kernel.org and you apply the patches in the correct order, 137 in the wrong directory. Less often, you'll find patches that need to be 179 So if you get these errors with kernel.org patches then you should probably 190 generate a patch representing the differences between two patches and then 193 step. The -z flag to interdiff will even let you feed it patches in gzip or 204 downloading and applying of patches (http://www.selenic.com/ketchup/). 213 Where can I download the patches? [all …]
|
D | SubmittingPatches | 18 Documentation/SubmittingDrivers; for device tree binding patches, read 19 Documentation/devicetree/bindings/submitting-patches.txt. 22 control system; if you use git to prepare your patches, you'll find much 24 and document a sensible set of patches. In general, use of git will make 43 patches prepared against those trees. See the "T:" entry for the subsystem 53 If you must generate your patches by hand, use "diff -up" or "diff -uprN" 54 to create patches. Git generates patches in this form by default; if 57 All changes to the Linux kernel occur in the form of patches, as 96 individual patches which modify things in logical stages; see section 120 vendor/product-specific trees that cherry-pick only specific patches [all …]
|
D | stable_kernel_rules.txt | 3 Rules on what kind of patches are accepted, and which ones are not, into the 30 Procedure for submitting patches to the -stable tree: 35 - Security patches should not be handled (solely) by the -stable review 77 Additionally, some patches submitted via Option 1 may have additional patch 93 Also, some patches may have kernel version prerequisites. This can be 114 - When the -stable maintainers decide for a review cycle, the patches will be 122 - At the end of the review cycle, the ACKed patches will be added to the 124 - Security patches will be accepted into the -stable tree directly from the 130 - The queues of patches, for both completed versions and in progress
|
D | HOWTO | 10 If anything in this document becomes out of date, please send in patches 99 patches if these rules are followed, and many people will only 109 Following these rules will not guarantee success (as all patches are 113 Other excellent descriptions of how to create patches properly are: 152 Documentation/applying-patches.txt 223 - 4.x -git kernel patches 224 - subsystem specific kernel trees and patches 234 Linus, usually the patches that have already been included in the 237 can be found at http://git-scm.com/) but plain patches are also just 240 only patches that do not include new features that could affect the [all …]
|
D | coccinelle.txt | 9 The semantic patches included in the kernel use features and options 61 Note that not all semantic patches implement all modes. For easy use 77 To produce patches, run: 90 positives. Thus, reports must be carefully checked, and patches 136 about semantic patches displayed, and no commit message proposed. 162 Proposing new semantic patches 165 New semantic patches can be proposed and submitted by kernel
|
D | SubmitChecklist | 9 kernel patches. 92 that it still works with all of the other queued patches and various
|
D | serial-console.txt | 106 for porting the patches from 2.1.4x to 2.1.6x for taking care of 107 the integration of these patches into m68k, ppc and alpha.
|
D | dontdiff | 190 patches*
|
D | SubmittingDrivers | 85 you because you get patches not bug reports. If you submit a 105 the author then patches will be redirected to them unless
|
D | 00-INDEX | 19 - brute force method of doing binary search of patches to find bug. 74 applying-patches.txt 75 - description of various trees and how to apply their patches. 181 - info on how to use e-mail to send un-mangled (git) patches.
|
D | kernel-docs.txt | 449 URL: http://www.moses.uklinux.net/patches/lki.html 658 the patches and describes them. Pointers to the patches are there, 693 Keywords: memory management, Linux-MM, mm patches, TODO, docs, 696 Memory related patches, HOWTOs, links, mm developers... Don't miss
|
D | iostats.txt | 4 Since 2.4.20 (and some versions before, with patches), and 2.5.45,
|
D | static-keys.txt | 66 http://gcc.gnu.org/ml/gcc-patches/2009-07/msg01556.html
|
D | robust-futexes.txt | 115 in userspace [just like with the previous patches].
|
D | CodingStyle | 234 Git will warn you about patches that introduce trailing whitespace, and can 236 of patches, this may make later patches in the series fail by changing their
|
D | svga.txt | 244 2.4 (18-Mar-96) Added patches by Hans Lermen fixing a memory overwrite problem
|
D | adding-syscalls.txt | 477 For more details, see https://www.kernel.org/doc/man-pages/patches.html
|
D | IPMI.txt | 545 patches and driver modifications. You can get those at the openipmi
|
D | devices.txt | 35 In particular, please don't sent patches for this list to Linus, at
|
/linux-4.4.14/drivers/scsi/aic7xxx/aicasm/ |
D | aicasm.c | 74 STAILQ_HEAD(patch_list, patch) patches; 126 STAILQ_INIT(&patches); in main() 425 for (cur_patch = STAILQ_FIRST(&patches); in output_code() 429 cur_patch == STAILQ_FIRST(&patches) ? "" : ",\n", in output_code() 494 pinfo = &scope->patches[patch]; in emit_patch() 516 STAILQ_INSERT_TAIL(&patches, new_patch, links); in emit_patch() 597 cur_patch = STAILQ_FIRST(&patches); in output_listing() 805 cur_scope->patches[1].skip_patch = in process_scope() 807 cur_scope->patches[1].skip_instr = in process_scope() 817 cur_scope->patches[0].skip_patch = patch0_patch_skip; in process_scope() [all …]
|
D | aicasm_symbol.h | 180 patch_info_t patches[2]; member
|
/linux-4.4.14/Documentation/development-process/ |
D | 5.Posting | 6 of conventions and procedures which are used in the posting of patches; 16 There is a constant temptation to avoid posting patches before they are 17 completely "ready." For simple patches, that is not a problem. If the 26 patches which are known to be half-baked, but those who do will come in 33 sending patches to the development community. These include: 57 The preparation of patches for posting can be a surprising amount of work, 75 up patches is a bit of an art; some developers spend a long time figuring 107 to a single file as 500 separate patches - an act which did not make him 113 patches, but to leave that infrastructure unused until the final patch 127 So now you have a perfect series of patches for posting, but the work is [all …]
|
D | 2.Process | 31 merging of patches for each release. At the beginning of each development 36 this time, at a rate approaching 1,000 changes ("patches," or "changesets") 52 Over the next six to ten weeks, only patches which fix problems should be 86 serious. For this reason, patches which cause regressions are looked upon 201 There is exactly one person who can merge patches into the mainline kernel 202 repository: Linus Torvalds. But, of the over 9,500 patches which went 220 maintainers to track a list of patches, including authorship information 222 patches in his or her repository are not found in the mainline. 225 the patches they have selected for merging from their repositories. If 226 Linus agrees, the stream of patches will flow up into his repository, [all …]
|
D | 7.AdvancedTopics | 19 Managing patches with git can make life much easier for the developer, 20 especially as the volume of those patches grows. Git also has its rough 35 understanding of how git works before trying to use it to make patches 45 Using git to generate patches for submission by email can be a good 61 Publicly-available branches should be created with care; merge in patches 111 mass movement of patches from one repository to another makes it easy to 114 thing happening; putting up a git tree with unreviewed or off-topic patches 117 You can send me patches, but for me to pull a git patch from you, I 124 To avoid this kind of situation, ensure that all patches within a given 131 If and when others start to send patches for inclusion into your tree, [all …]
|
D | 6.Followthrough | 5 patches. One of the biggest mistakes that even experienced kernel 7 posting patches indicates a transition into the next stage of the process, 16 prevent the inclusion of your patches into the mainline. 77 that your patches go nowhere. 107 dedicated to patches planned for the next merge window, and another for 110 For patches applying to areas for which there is no obvious subsystem tree 111 (memory management patches, for example), the default tree often ends up 125 burner so that the remaining patches can be worked into shape and merged. 127 developers and, possibly, moving some patches between trees to ensure that 166 for; you can start creating cool new patches once any problems with the old [all …]
|
D | 1.Intro | 35 patches are covered, and there is an introduction to some of the tools 36 which can help to ensure that kernel patches are correct. 38 Section 5 talks about the process of posting patches for review. To be 39 taken seriously by the development community, patches must be properly 44 Section 6 covers what happens after posting patches; the job is far from 50 Section 7 introduces a couple of "advanced" topics: managing patches with 51 git and reviewing patches posted by others.
|
D | 4.Coding | 43 reformatting patches as a way of gaining familiarity with the process, or 75 patches to remove unused arguments; they should, in general, not be added 295 problems. Quite a few "semantic patches" for the kernel have been packaged 297 through those semantic patches and report on any problems found. See
|
D | 3.Early-stage | 137 patches, and who, if anybody, is attaching Signed-off-by lines to those 138 patches. Those are the people who will be best placed to help with a new
|
/linux-4.4.14/Documentation/arm/SA1100/ |
D | Brutus | 53 The actual Brutus support may not be complete without extra patches. 54 If such patches exist, they should be found from 63 Please send patches to nico@fluxnic.net
|
D | Assabet | 31 patches were merged into BLOB to add support for Assabet. 38 John Dorsey has produced add-on patches to add support for Assabet and 56 ftp://ftp.handhelds.org/pub/linux/arm/sa-1100-patches/
|
/linux-4.4.14/ |
D | .gitignore | 78 patches-* 81 patches
|
D | README | 84 that there are no failed patches (some-file-name# or some-file-name.rej). 87 Unlike patches for the 4.x kernels, patches for the 4.x.y kernels 91 and 4.0.2 patches. Similarly, if you are running kernel version 4.0.2 and 94 Documentation/applying-patches.txt 98 patches found.
|
D | CREDITS | 50 D: NFS over TCP patches 57 W: http://www.moses.uklinux.net/patches 60 D: Various kernel patches 415 D: wrote /proc/self hack, minor samba & dosemu patches 824 D: Various kernel patches 893 D: Dell PowerEdge server, SCSI layer, misc drivers, and other patches 1301 D: Many other patches, documentation files, mini kernels, utilities, ... 1331 D: Miscellaneous ipv4 sysctl patches 1344 D: Various AX.25/ROSE/NETROM + hamradio driver patches 1345 D: Various X.25/LABP + driver patches [all …]
|
D | REPORTING-BUGS | 129 [X.] Other notes, patches, fixes, workarounds: 139 bug reports. That may include running new tests, applying patches,
|
D | MAINTAINERS | 72 M: Mail patches to: FullName <address@domain> 74 These reviewers should be CCed on patches. 113 matches patches or files that contain "of_get_profile" 115 matches patches or files that contain one or more of the words 3422 T: quilt http://people.redhat.com/agk/patches/linux/editing/ 10773 T: quilt http://svn.sourceforge.jp/svnroot/tomoyo/trunk/2.5.x/tomoyo-lsm/patches/ 11676 L: patches@opensource.wolfsonmicro.com
|
/linux-4.4.14/Documentation/scsi/ |
D | lpfc.txt | 16 as of 2.6.12. We no longer need to provide patches for this support, 62 By default, the driver expects the patches for block/unblock interfaces 81 Thankfully, at this time, patches are not needed.
|
D | dc395x.txt | 15 Problems, questions and patches should be submitted to the mailing
|
D | tmscsim.txt | 65 my web page and apply the patch. Apply further patches to upgrade to the 72 You should apply the three patches included in dc390-120-kernel.diff 74 The patches are against 2.1.125, so you might have to manually resolve 77 The patches will update the kernel startup code to allow boot parameters to 86 contact me to get the appropriate patches.
|
D | aha152x.txt | 5 TC1550 patches by Luuk van Dijk (ldz@xs4all.nl)
|
D | scsi-changer.txt | 162 I wrote this driver using the famous mailing-patches-around-the-world
|
D | osst.txt | 169 I did add some patches to those drivers as well and coordinated things a
|
D | ChangeLog.1992-1997 | 760 hog memory). Use other patches which got lost from 1.1.68. 1042 * pas16.c: Add a few patches (Drew?). 1365 Changes based upon patches in Yggdrasil distribution.
|
D | ncr53c8xx.txt | 132 Latest driver version and patches are available at: 1149 patches:
|
D | ChangeLog.lpfc | 53 * Merged patch from Christoph Hellwig (3/19): some misc patches 707 * Integrate patches from Christoph Hellwig: two new helpers common
|
/linux-4.4.14/drivers/usb/usbip/ |
D | README | 7 Please send patches for this code to Greg Kroah-Hartman <greg@kroah.com>
|
/linux-4.4.14/drivers/staging/skein/ |
D | TODO | 7 Please send patches to Jason Cooper <jason@lakedaemon.net> in addition to the
|
/linux-4.4.14/drivers/staging/panel/ |
D | TODO | 7 Please send patches to Greg Kroah-Hartman <greg@kroah.com> and
|
/linux-4.4.14/Documentation/video4linux/ |
D | README.saa7134 | 24 Pick up videodev + v4l2 patches from http://bytesex.org/patches/.
|
D | README.davinci-vpbe | 93 - Add support for fbdev drivers.- Ready and part of subsequent patches.
|
/linux-4.4.14/sound/oss/ |
D | README.FIRST | 1 The modular sound driver patches were funded by Red Hat Software
|
/linux-4.4.14/drivers/staging/comedi/ |
D | TODO | 8 Please send patches to Greg Kroah-Hartman <greg@kroah.com> and
|
/linux-4.4.14/drivers/thermal/ti-soc-thermal/ |
D | TODO | 12 Copy patches to Eduardo Valentin <eduardo.valentin@ti.com>
|
/linux-4.4.14/drivers/staging/netlogic/ |
D | TODO | 5 Please send patches
|
/linux-4.4.14/drivers/staging/gs_fpgaboot/ |
D | TODO | 5 Please send any patches for this driver to Insop Song<insop.song@gainspeed.com>
|
/linux-4.4.14/drivers/staging/olpc_dcon/ |
D | TODO | 6 Please send patches to Greg Kroah-Hartman <greg@kroah.com> and
|
/linux-4.4.14/Documentation/video4linux/bttv/ |
D | README | 52 in bttv-cards.c (in case you are intrested or want to mail patches 63 yourself (patches very welcome of course...) You know: The linux 81 Finally: If you mail some patches for bttv around the world (to
|
/linux-4.4.14/drivers/staging/wlan-ng/ |
D | README | 6 Please send any patches or complaints about this driver to Greg
|
/linux-4.4.14/drivers/staging/rtl8712/ |
D | TODO | 7 Please send any patches to Greg Kroah-Hartman <greg@kroah.com>,
|
/linux-4.4.14/drivers/staging/mt29f_spinand/ |
D | TODO | 7 Please send patches
|
/linux-4.4.14/scripts/ksymoops/ |
D | README | 5 with patches to other utilities in order to give more accurate Oops
|
/linux-4.4.14/drivers/staging/dgnc/ |
D | TODO | 9 Please send patches to Greg Kroah-Hartman <greg@kroah.com> and
|
/linux-4.4.14/drivers/staging/xgifb/ |
D | TODO | 12 Please send patches to:
|
/linux-4.4.14/drivers/staging/vt6656/ |
D | TODO | 18 Please send any patches to Greg Kroah-Hartman <greg@kroah.com>
|
/linux-4.4.14/drivers/staging/lustre/ |
D | TODO | 11 Please send any patches to Greg Kroah-Hartman <greg@kroah.com>, Andreas Dilger
|
/linux-4.4.14/Documentation/virtual/kvm/ |
D | 00-INDEX | 22 - review checklist for KVM patches.
|
D | review-checklist.txt | 1 Review checklist for kvm patches
|
D | nested-vmx.txt | 40 Additional patches for running Windows under guest KVM, and Linux under 233 These patches were written by:
|
/linux-4.4.14/drivers/staging/vt6655/ |
D | TODO | 20 Please send any patches to Greg Kroah-Hartman <greg@kroah.com>
|
/linux-4.4.14/drivers/staging/media/lirc/ |
D | TODO | 10 Please send patches to:
|
/linux-4.4.14/drivers/staging/sm750fb/ |
D | TODO | 12 Please send any patches to
|
/linux-4.4.14/Documentation/networking/ |
D | xfrm_sync.txt | 2 The sync patches work is based on initial patches from 3 Krisztian <hidden@balabit.hu> and others and additional patches 13 These patches add ability to sync and have accurate lifetime byte (to
|
D | netdev-FAQ.txt | 109 A: Generally speaking, the patches get triaged quickly (in less than 48h). 114 Q: How can I tell what patches are queued up for backporting to the 118 for networking, Dave collects up patches he deems critical for the 124 It contains the patches which Dave has selected, but not yet handed
|
D | fore200e.txt | 64 patches/improvement/comments/flames to <lizzi@cnam.fr>.
|
D | README.ipw2100 | 51 patches, utilities, or code with the Intel wireless LAN adapters that 52 have been manipulated by an unauthorized party (i.e., patches, 87 potential fixes and patches, as well as links to the development mailing list
|
D | igbvf.txt | 28 not supplying patches against the kernel source to allow for static linking
|
D | generic-hdlc.txt | 131 For patches and other info look at:
|
D | dm9000.txt | 16 maintained and tested by Ben Dooks, who should be CC: to any patches for this
|
D | README.ipw2200 | 64 patches, utilities, or code with the Intel wireless LAN adapters that 65 have been manipulated by an unauthorized party (i.e., patches,
|
D | 00-INDEX | 234 - sync patches for XFRM enable migration of an SA between hosts.
|
D | scaling.txt | 437 2.6.38. Original patches were submitted by Tom Herbert 440 Accelerated RFS was introduced in 2.6.35. Original patches were
|
D | vortex.txt | 446 asks more questions, asks for more tests, asks for patches to be
|
D | arcnet.txt | 100 without patches, though, and also doesn't like several cards. Fixed
|
D | bonding.txt | 28 beowulf patches for kernel 2.0. It has changed quite a bit since, and
|
/linux-4.4.14/drivers/staging/rtl8723au/ |
D | TODO | 12 Please send any patches to Greg Kroah-Hartman <gregkh@linux.com>,
|
/linux-4.4.14/drivers/staging/rtl8188eu/ |
D | TODO | 18 Please send any patches to Greg Kroah-Hartman <gregkh@linux.com>,
|
/linux-4.4.14/drivers/of/unittest-data/ |
D | testcases.dts | 19 * phandle fixup data - generated by dtc patches that aren't upstream.
|
/linux-4.4.14/drivers/staging/slicoss/ |
D | TODO | 32 Please send patches to:
|
/linux-4.4.14/drivers/staging/fsl-mc/ |
D | TODO | 26 Please send any patches to Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
|
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
D | SMDK2440.txt | 27 Some of the h1940 patches that can be found from the H1940 project
|
D | Overview.txt | 140 Documentation/arm directory before submitting patches. The 142 located at http://www.arm.linux.org.uk/developer/patches/
|
/linux-4.4.14/Documentation/cpu-freq/ |
D | index.txt | 37 you can report bugs, problems or submit patches. To post a message,
|
/linux-4.4.14/drivers/staging/android/ |
D | TODO | 28 Please send patches to Greg Kroah-Hartman <greg@kroah.com> and Cc:
|
/linux-4.4.14/Documentation/ja_JP/ |
D | SubmittingPatches | 713 Andi Kleen, "On submitting kernel patches" 715 http://halobates.de/on-submitting-patches.pdf
|
D | HOWTO | 189 Documentation/applying-patches.txt
|
/linux-4.4.14/Documentation/filesystems/ |
D | bfs.txt | 54 If you have any patches, questions or suggestions regarding this BFS
|
D | ext4.txt | 108 * Online defrag (patches available but not well tested) 116 metadata checksumming have been discussed and planned for a bit but no patches
|
D | ext2.txt | 72 separate patches). There is also a versioning mechanism to allow new
|
D | f2fs.txt | 25 For reporting bugs and sending patches, please use the following mailing list:
|
D | proc.txt | 67 additions and patches are welcome and will be added to this document if you
|
/linux-4.4.14/Documentation/devicetree/bindings/ |
D | submitting-patches.txt | 2 Submitting devicetree (DT) binding patches
|
/linux-4.4.14/arch/x86/ |
D | Makefile_32.cpu | 23 # Please note, that patches that add -march=athlon-xp and friends are pointless.
|
/linux-4.4.14/Documentation/powerpc/ |
D | cpu_features.txt | 32 After detecting the processor type, the kernel patches out sections of code
|
/linux-4.4.14/Documentation/ide/ |
D | ChangeLog.ide-floppy.1996-2002 | 3 * ALPHA patches to this driver on an EASYSTOR LS-120 ATAPI floppy drive.
|
D | ChangeLog.ide-cd.1994-2004 | 75 * More workarounds for Vertos bugs (based on patches 95 * 3.12 May 7, 1996 -- Rudimentary changer support. Based on patches
|
/linux-4.4.14/Documentation/dvb/ |
D | contributors.txt | 1 Thanks go to the following people for patches and contributions:
|
/linux-4.4.14/Documentation/power/ |
D | video.txt | 101 Acer TM 800 vga=normal, X patches, see webpage (5) or vbetool (6) 102 Acer TM 803 vga=normal, X patches, see webpage (5) or vbetool (6)
|
D | swsusp.txt | 152 suspend-to-disk which is available as separate patches for 2.4 and 2.6
|
/linux-4.4.14/Documentation/accounting/ |
D | taskstats.txt | 12 - extensibility for use by future accounting patches 137 per-task/process stats as patches to collect them get added to the kernel
|
/linux-4.4.14/Documentation/arm/ |
D | README | 43 Please send patches to the patch system. For more information, see 44 http://www.arm.linux.org.uk/developer/patches/info.php Always include some
|
D | IXP4xx | 162 The following people have contributed patches/comments/etc:
|
/linux-4.4.14/Documentation/block/ |
D | biodoc.txt | 27 over discussions, prior patches and the collective experience of several 37 The following people helped with fixes/contributions to the bio patches 77 8. A list of prior/related/impacted patches/ideas 490 and readahead patches. 846 Andrew Morton's multi-page bio patches attempt to issue multi-page 1145 8. Prior/Related/Impacted patches 1147 8.1. Earlier kiobuf patches (sct/axboe/chait/hch/mkp) 1148 - orig kiobuf & raw i/o patches (now in 2.4 tree) 1154 8.3. SGI XFS - pagebuf patches - use of kiobufs 1163 8.10. Write clustering patches ? (Marcelo/Quintela/Riel ?) [all …]
|
D | data-integrity.txt | 131 The data integrity patches add a new field to struct bio when
|
/linux-4.4.14/Documentation/sound/oss/ |
D | btaudio | 35 driver is in the bttv tarball. Kernel patches might be available too,
|
D | mwave | 11 latest MWAVE patches. So, in other words, don't bypass the test for MWAVES!
|
D | README.OSS | 12 patches, contributions or suggestions send them to Alan: I'm sure they are 91 patches and your name is not in the above list, please inform me. 93 Sending your contributions or patches 103 sending me patches relative to production kernels. 562 if you like to use these patches with SoftOSS included in OSS/Free.
|
D | Introduction | 51 The modular sound driver patches were funded by Red Hat Software
|
/linux-4.4.14/fs/reiserfs/ |
D | Kconfig | 12 large directories and small files. Additional patches are needed
|
D | README | 149 the endian safe patches which allow ReiserFS to run on any platform
|
/linux-4.4.14/Documentation/fb/ |
D | intelfb.txt | 146 6. Andrew Morton for his kernel patches maintenance.
|
D | modedb.txt | 151 (feel free to send patches). The DRM drivers also support this.
|
D | sstfb.txt | 28 You can apply the patches found in sstfb/kernel/*-2.{2|4}.x.patch,
|
/linux-4.4.14/Documentation/ko_KR/ |
D | HOWTO | 162 Documentation/applying-patches.txt
|
/linux-4.4.14/Documentation/isdn/ |
D | HiSax.cert | 72 Please send any changes, bugfixes and patches to me rather than implementing
|
D | README.gigaset | 410 for his kernel 2.6 patches 414 for his logs and patches to get cx 100 working
|
/linux-4.4.14/Documentation/security/ |
D | IMA-templates.txt | 37 (new function defined within the patches for the new template management
|
/linux-4.4.14/Documentation/hwmon/ |
D | hwmon-kernel-api.txt | 18 also read Documentation/hwmon/submitting-patches.
|
D | submitting-patches | 4 This text is a collection of suggestions for people writing patches or
|
/linux-4.4.14/Documentation/zh_CN/ |
D | HOWTO | 144 Documentation/applying-patches.txt
|
/linux-4.4.14/Documentation/usb/ |
D | usb-serial.txt | 258 accept patches. An urb queue or packet buffer would likely fit the bill here. 260 If you have any questions, problems, patches, feature requests, etc. you can 263 (your problems/patches can alternately be submitted to usb-devel)
|
D | dma.txt | 83 feel free to submit patches.
|
D | gadget-testing.txt | 721 with these patches:
|
/linux-4.4.14/Documentation/crypto/ |
D | api-intro.txt | 130 For further patches and various updates, including the current TODO
|
/linux-4.4.14/Documentation/laptops/ |
D | asus-laptop.txt | 253 Any other comments or patches are also more than welcome.
|
D | laptop-mode.txt | 560 # (A couple of early 2.6 laptop mode patches had these.)
|
D | thinkpad-acpi.txt | 62 Any other comments or patches are also more than welcome.
|
/linux-4.4.14/Documentation/fmc/ |
D | identifiers.txt | 35 more items of the FRU standard for your boards, please submit patches.
|
/linux-4.4.14/Documentation/timers/ |
D | hrtimers.txt | 66 clock capabilities, and patches for that exist and are maturing quickly.
|
/linux-4.4.14/fs/affs/ |
D | Changes | 129 patches he did. They're marked (BH). Thanks, Bill!
|
/linux-4.4.14/Documentation/RCU/ |
D | checklist.txt | 4 This document contains a checklist for producing and reviewing patches 7 would cause. This list is based on experiences reviewing such patches
|
D | RTFP.txt | 106 abundance of RCU patches was presented the following year [McKenney02a], 648 Described RCU, and presented some patches implementing and using 934 ,Title="RCU low latency patches" 1037 RCU runs reasonably on a 512-CPU SGI using Manfred Spraul's patches, 1308 First publication of working lock-based deferred free patches 1891 Final patch for preemptable RCU to -rt. (Later patches were
|
D | whatisRCU.txt | 589 forget about them when submitting patches making use of RCU!]
|
/linux-4.4.14/Documentation/PCI/ |
D | pci-error-recovery.txt | 413 >>> patches implementing error recovery. Not all of these patches are in
|
D | pci.txt | 24 Please send questions/comments/patches about Linux PCI API to the
|
/linux-4.4.14/Documentation/sound/alsa/ |
D | timestamping.txt | 103 precise start time (patches WIP)
|
D | ALSA-Configuration.txt | 145 Load the std.sb and drums.sb patches also supplied by sbiload:
|
/linux-4.4.14/Documentation/s390/ |
D | 3270.txt | 77 patches. Then do
|
/linux-4.4.14/fs/befs/ |
D | ChangeLog | 406 Resolve rejected patches
|
/linux-4.4.14/Documentation/virtual/uml/ |
D | UserModeLinux-HOWTO.txt | 413 Note that UML kernel patches may require a specific version of the 4342 of patches, fixes, and clues 4345 Lennert Buytenhek - Contributed various patches, a rewrite of the 4354 plus various other small patches. 4360 the occasional patch. I like patches. 4373 submitted patches for the slip transport and lots of other things.
|
/linux-4.4.14/Documentation/input/ |
D | elantech.txt | 9 Version 2 (EeePC) hardware support based on patches
|
/linux-4.4.14/drivers/scsi/aic7xxx/ |
D | aic7xxx_core.c | 6886 cur_patch = patches; in ahc_loadseq() 6966 num_patches = ARRAY_SIZE(patches); in ahc_check_patch() 6967 last_patch = &patches[num_patches]; in ahc_check_patch() 7031 cur_patch = patches; in ahc_download_instr()
|
D | aic79xx_seq.h_shipped | 1035 } patches[] = {
|
D | aic7xxx_seq.h_shipped | 1089 } patches[] = {
|
D | aic79xx_core.c | 9454 cur_patch = patches; in ahd_loadseq() 9519 num_patches = ARRAY_SIZE(patches); in ahd_check_patch() 9520 last_patch = &patches[num_patches]; in ahd_check_patch() 9556 cur_patch = patches; in ahd_resolve_seqaddr()
|
/linux-4.4.14/Documentation/arm64/ |
D | acpi_object_usage.txt | 320 any driver patches for discussion, especially when
|
/linux-4.4.14/arch/arm/tools/ |
D | mach-types | 9 # Please do not send patches to this file; it is automatically generated!
|
/linux-4.4.14/drivers/block/ |
D | Kconfig | 239 kernel patches. The vanilla kernel offers the cryptoloop option
|
/linux-4.4.14/Documentation/kbuild/ |
D | makefiles.txt | 1336 $(EXTRAVERSION) defines an even tinier sublevel for pre-patches 1337 or additional patches. It is usually some non-numeric string
|
/linux-4.4.14/drivers/ata/ |
D | Kconfig | 10 configuration structure without having to submit endless patches
|
/linux-4.4.14/Documentation/scheduler/ |
D | sched-deadline.txt | 471 throttling patches [https://lkml.org/lkml/2010/2/23/239] but we still are in
|
/linux-4.4.14/drivers/gpio/ |
D | Kconfig | 82 custom patches. In those cases, userspace code may import
|
/linux-4.4.14/Documentation/blockdev/ |
D | README.DAC960 | 223 are patches to LILO 20 and FDISK v2.8 that add DAC960 support, along with
|
/linux-4.4.14/scripts/genksyms/ |
D | parse.tab.c_shipped | 1255 <http://lists.gnu.org/archive/html/bison-patches/2009-12/msg00024.html>
|
/linux-4.4.14/Documentation/m68k/ |
D | kernel-options.txt | 21 patches.
|
/linux-4.4.14/scripts/kconfig/ |
D | zconf.tab.c_shipped | 1218 <http://lists.gnu.org/archive/html/bison-patches/2009-12/msg00024.html>
|
/linux-4.4.14/Documentation/cdrom/ |
D | cdrom-standard.tex | 709 even send in our own patches to the programs. The use of $O_NONBLOCK$
|
/linux-4.4.14/Documentation/devicetree/ |
D | booting-without-of.txt | 75 patches, will be fwd separately).
|
/linux-4.4.14/drivers/staging/speakup/ |
D | spkguide.txt | 25 http://linux-speakup.org/. Speakup is a set of patches to the standard
|