| /linux-2.6.39/Documentation/ |
| D | email-clients.txt | 13 Email clients that are used for Linux kernel patches should send the
17 Don't send patches with "format=flowed". This can cause unexpected
24 Emailed patches should be in ASCII or UTF-8 encoding only.
31 Copy-and-paste (or cut-and-paste) usually does not work for patches
36 Don't use PGP/GPG signatures in mail that contains patches.
37 This breaks many scripts that read and apply the patches.
41 and successfully apply it with 'patch' before sending patches to Linux
48 patches for the Linux kernel. These are not meant to be complete
71 Some people use this successfully for patches.
87 Some people use Kmail 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 | stable_kernel_rules.txt | 3 Rules on what kind of patches are accepted, and which ones are not, into the
24 Procedure for submitting patches to the -stable tree:
34 - If the patch requires other patches as prerequisites which can be
55 - Security patches should not be sent to this alias, but instead to the
61 - When the -stable maintainers decide for a review cycle, the patches will be
69 - At the end of the review cycle, the ACKed patches will be added to the
71 - Security patches will be accepted into the -stable tree directly from the
|
| 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 - 2.6.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 the 'virtual rule'
39 The semantic patches in the kernel will work best with Coccinelle version
64 Note that not all semantic patches implement all modes. For easy use
74 To produce patches, run:
87 positives. Thus, reports must be carefully checked, and patches
124 In this mode, there is no information about semantic patches
128 Proposing new semantic patches
131 New semantic patches can be proposed and submitted by kernel
|
| D | SubmittingPatches | 28 Use "diff -up" or "diff -uprN" to create patches.
30 All changes to the Linux kernel occur in the form of patches, as
71 splitting them into individual patches which modify things in
120 or more patches. If your changes include an API update, and a new
121 driver which uses that new API, separate those into two patches.
131 If you cannot condense your patch set into a smaller set of patches,
143 At a minimum you should check your patches with the patch style
161 Do not send more than 15 patches at once to the vger mailing lists!!!
200 For small patches you may want to CC the Trivial Patch Monkey
201 trivial@kernel.org which collects "trivial" patches. Have a look
[all …]
|
| /linux-2.6.39/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 …]
|
| /linux-2.6.39/drivers/staging/ath6kl/ |
| D | TODO | 14 patches will break pretty much any other patches. Please use IRC to
20 Send patches to:
|
| /linux-2.6.39/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 …]
|
| /linux-2.6.39/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
|
| /linux-2.6.39/ |
| D | .gitignore | 62 patches-*
65 patches
|
| /linux-2.6.39/drivers/staging/cx25821/ |
| D | README | 5 Please send patches to linux-media@vger.kernel.org
|
| /linux-2.6.39/drivers/staging/usbip/ |
| D | README | 6 Please send patches for this code to Greg Kroah-Hartman <greg@kroah.com>
|
| /linux-2.6.39/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.
|
| /linux-2.6.39/drivers/staging/echo/ |
| D | TODO | 4 Please send patches to Greg Kroah-Hartman <greg@kroah.com> and Cc: Steve
|
| /linux-2.6.39/drivers/staging/go7007/ |
| D | go7007.txt | 410 The WIS PCI Voyager driver requires several patches to the Linux 2.6.11.x
411 kernel source tree before compiling the driver. These patches update the
415 The following patches must be downloaded from Gerd Knorr's website and
418 http://dl.bytesex.org/patches/2.6.11-2/i2c-tuner
419 http://dl.bytesex.org/patches/2.6.11-2/i2c-tuner2
420 http://dl.bytesex.org/patches/2.6.11-2/v4l2-api-mpeg
421 http://dl.bytesex.org/patches/2.6.11-2/saa7134-update
423 The following patches are included with this SDK and can be applied in any
426 patches/2.6.11/saa7134-voyager.diff
427 patches/2.6.11/tda8275-newaddr.diff
[all …]
|
| /linux-2.6.39/drivers/staging/sbe-2t3e3/ |
| D | TODO | 6 Please send patches to Krzysztof Halasa <khc@pm.waw.pl>.
|
| /linux-2.6.39/drivers/staging/tm6000/ |
| D | TODO | 8 Please send patches to linux-media@vger.kernel.org
|
| /linux-2.6.39/drivers/staging/westbridge/ |
| D | TODO | 6 Please send any patches to Greg Kroah-Hartman <gregkh@suse.de>
|
| /linux-2.6.39/drivers/staging/panel/ |
| D | TODO | 8 Please send patches to Greg Kroah-Hartman <greg@kroah.com> and
|
| /linux-2.6.39/Documentation/video4linux/ |
| D | README.saa7134 | 24 Pick up videodev + v4l2 patches from http://bytesex.org/patches/.
|
| /linux-2.6.39/sound/oss/ |
| D | README.FIRST | 1 The modular sound driver patches were funded by Red Hat Software
|