Lines Matching refs:patches
3 Posting patches
9 of conventions and procedures which are used in the posting of patches;
13 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
20 There is a constant temptation to avoid posting patches before they are
21 completely "ready." For simple patches, that is not a problem. If the
30 patches which are known to be half-baked, but those who do will come in
34 Before creating patches
38 sending patches to the development community. These include:
63 The preparation of patches for posting can be a surprising amount of work,
81 up patches is a bit of an art; some developers spend a long time figuring
113 to a single file as 500 separate patches - an act which did not make him
119 patches, but to leave that infrastructure unused until the final patch
134 So now you have a perfect series of patches for posting, but the work is
201 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
230 which can be found in :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
238 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`.
248 …see the reviewer's statement in :ref:`Documentation/process/submitting-patches.rst <submittingpatc…
260 Be careful in the addition of tags to your patches, as only Cc: is appropriate
269 Before you mail your patches, there are a couple of other things you should
272 - Are you sure that your mailer will not corrupt the patches? Patches
279 helpful hints on making specific mail clients work for sending patches.
282 run patches through scripts/checkpatch.pl and address the complaints it
284 embodiment of a fair amount of thought about what kernel patches should
293 When mailing patches, it is important to send copies to anybody who might
320 is possible to send patches directly to Linus Torvalds and have him merge
323 you will be wanting that maintainer to merge your patches. If there is no
334 patches in the series, and "subsys" is the name of the affected subsystem.
337 If you have a significant series of patches, it is customary to send an
341 that the patches, themselves, have complete changelog information.
346 patches with the proper threading. If you have a long series, though, and