Lines Matching refs:patches

3 Submitting patches: the essential guide to getting your code into the kernel
17 tree binding patches, read
18 Documentation/devicetree/bindings/submitting-patches.rst.
20 This documentation assumes that you're using ``git`` to prepare your patches.
40 patches prepared against those trees.  See the **T:** entry for the subsystem
60 vendor/product-specific trees that cherry-pick only specific patches
168 or more patches.  If your changes include an API update, and a new
169 driver which uses that new API, separate those into two patches.
183 When dividing your change into a series of patches, take special care to
189 If you cannot condense your patch set into a smaller set of patches,
210 Check your patches with the patch style checker prior to submission
231 your patches as arguments to scripts/get_maintainer.pl).  If you cannot find a
237 for all patches, but the volume on that list has caused a number of
246 Do not send more than 15 patches at once to the vger mailing lists!!!
250 He gets a lot of e-mail, and, at this point, very few patches go through
284 For this reason, all patches should be submitted by e-mail "inline". The
302 Exception:  If your mailer is mangling patches then someone may ask
306 your e-mail client so that it sends your patches untouched.
323 version, add a ``patch changelog`` to the cover letter or to individual patches
338 Once upon a time, patches used to disappear into the void without comment,
341 that you have sent your patches to the right place.  Wait for a minimum of
361 and other kernel developers more easily distinguish patches from other
370 To improve tracking of who did what, especially with patches that can
373 patches that are being emailed around.
508 future patches, and ensures credit for the testers.
546 or reviewer, should be added by author to the applicable patches when sending
577 that, if you have your patches stored in a ``git`` repository, proper patch
616 series`` is an ordered sequence of multiple, related patches).
625 thousands of patches using tools such as ``gitk`` or ``git log
642 If there are four patches in a patch series the individual patches may
644 understand the order in which the patches should be applied and that
645 they have reviewed or applied all of the patches in the patch series.
685 on bigger patches. If you are going to include a ``diffstat`` after the
758 When other developers receive your patches and start the review process,
764 If you are using ``git format-patch`` to generate your patches, you can
787     $ git am patches.mbox
798 If you are not using git to format your patches, you can still include
836 Andi Kleen, "On submitting kernel patches"
839   http://halobates.de/on-submitting-patches.pdf