Lines Matching full:your
3 Submitting patches: the essential guide to getting your code into the kernel
9 can greatly increase the chances of your change being accepted.
19 This documentation assumes that you're using ``git`` to prepare your patches.
21 use it, it will make your life as a kernel developer and in general much
45 Describe your changes
48 Describe your problem. Whether your patch is a one-line bug fix or
60 from upstream, so include anything that could help route your change
69 different workloads. Describe the expected downsides of your
77 The maintainer will thank you if you write your patch description in a
81 Solve only one problem per patch. If your description starts to get
82 long, that's a sign that you probably need to split up your patch.
94 Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
112 there is no collision with your six-character ID now, that condition may
116 can be found on the web, add 'Link:' tags pointing to it. In case your patch
132 However, try to make your explanation understandable without external
137 If your patch fixes a bug in a specific commit, e.g. you found an issue using
160 Separate your changes
165 For example, if your changes include both bug fixes and performance
167 or more patches. If your changes include an API update, and a new
180 in your patch description.
182 When dividing your change into a series of patches, take special care to
185 splitting your patch series at any point; they will not thank you if you
188 If you cannot condense your patch set into a smaller set of patches,
193 Style-check your changes
196 Check your patch for basic style violations, details of which can be
199 the reviewers time and will get your patch rejected, probably
205 moving the code and your changes. This greatly aids review of the
209 Check your patches with the patch style checker prior to submission
211 viewed as a guide, not as a replacement for human judgment. If your code
219 You should be able to justify all violations that remain in your
223 Select the recipients for your patch
230 your patches as arguments to scripts/get_maintainer.pl). If you cannot find a
235 of your patch set. linux-kernel@vger.kernel.org should be used by default
238 subsystem-specific list; your patch will probably get more attention there.
250 Linus directly, so typically you should do your best to -avoid-
264 into the sign-off area of your patch (note, NOT an email recipient). You
280 developer to be able to "quote" your changes, using standard e-mail
281 tools, so that they may comment on specific portions of your code.
292 Be wary of your editor's word-wrap corrupting your patch,
293 if you choose to cut-n-paste your patch.
297 attachment as plain text, making it impossible to comment on your
299 decreasing the likelihood of your MIME-attached change being accepted.
301 Exception: If your mailer is mangling patches then someone may ask
305 your e-mail client so that it sends your patches untouched.
310 Your patch will almost certainly get comments from reviewers on ways in
311 which the patch can be improved, in the form of a reply to your email. You must
334 After you have submitted your change, be patient and wait. Reviewers are
335 busy people and may not get to your patch right away.
340 that you have sent your patches to the right place. Wait for a minimum of
349 Don't add "RESEND" when you are submitting a modified version of your
359 convention to prefix your subject line with [PATCH]. This lets Linus
366 Sign your work - the Developer's Certificate of Origin
410 using your real name (sorry, no pseudonyms or anonymous contributions.)
542 increase the likelihood of your patch getting into the kernel.
561 which stable kernel versions should receive your fix. This is the preferred
576 that, if you have your patches stored in a ``git`` repository, proper patch
617 Bear in mind that the ``summary phrase`` of your email becomes a
757 When other developers receive your patches and start the review process,
759 should place your work. This is particularly useful for automated CI
761 the quality of your submission before the maintainer starts the review.
763 If you are using ``git format-patch`` to generate your patches, you can
764 automatically include the base tree information in your submission by
772 [perform your edits and commits]
797 If you are not using git to format your patches, you can still include
799 on which your work is based. You should add it either in the cover
802 content, right before your email signature.