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
41 Describe your changes
44 Describe your problem. Whether your patch is a one-line bug fix or
56 from upstream, so include anything that could help route your change
65 different workloads. Describe the expected downsides of your
73 The maintainer will thank you if you write your patch description in a
77 Solve only one problem per patch. If your description starts to get
78 long, that's a sign that you probably need to split up your patch.
90 Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
101 However, try to make your explanation understandable without external
119 there is no collision with your six-character ID now, that condition may
122 If your patch fixes a bug in a specific commit, e.g. you found an issue using
145 Separate your changes
150 For example, if your changes include both bug fixes and performance
152 or more patches. If your changes include an API update, and a new
165 in your patch description.
167 When dividing your change into a series of patches, take special care to
170 splitting your patch series at any point; they will not thank you if you
173 If you cannot condense your patch set into a smaller set of patches,
178 Style-check your changes
181 Check your patch for basic style violations, details of which can be
184 the reviewers time and will get your patch rejected, probably
190 moving the code and your changes. This greatly aids review of the
194 Check your patches with the patch style checker prior to submission
196 viewed as a guide, not as a replacement for human judgment. If your code
204 You should be able to justify all violations that remain in your
208 Select the recipients for your patch
219 of your patch set. linux-kernel@vger.kernel.org should be used by default
222 subsystem-specific list; your patch will probably get more attention there.
234 Linus directly, so typically you should do your best to -avoid-
248 into the sign-off area of your patch (note, NOT an email recipient). You
283 developer to be able to "quote" your changes, using standard e-mail
284 tools, so that they may comment on specific portions of your code.
295 Be wary of your editor's word-wrap corrupting your patch,
296 if you choose to cut-n-paste your patch.
300 attachment as plain text, making it impossible to comment on your
302 decreasing the likelihood of your MIME-attached change being accepted.
304 Exception: If your mailer is mangling patches then someone may ask
308 your e-mail client so that it sends your patches untouched.
313 Your patch will almost certainly get comments from reviewers on ways in
314 which the patch can be improved, in the form of a reply to your email. You must
333 After you have submitted your change, be patient and wait. Reviewers are
334 busy people and may not get to your patch right away.
339 that you have sent your patches to the right place. Wait for a minimum of
348 Don't add "RESEND" when you are submitting a modified version of your
358 convention to prefix your subject line with [PATCH]. This lets Linus
365 Sign your work - the Developer's Certificate of Origin
409 using your real name (sorry, no pseudonyms or anonymous contributions.)
540 increase the likelihood of your patch getting into the kernel.
559 which stable kernel versions should receive your fix. This is the preferred
574 that, if you have your patches stored in a ``git`` repository, proper patch
615 Bear in mind that the ``summary phrase`` of your email becomes a
753 When other developers receive your patches and start the review process,
755 should place your work. This is particularly useful for automated CI
757 the quality of your submission before the maintainer starts the review.
759 If you are using ``git format-patch`` to generate your patches, you can
760 automatically include the base tree information in your submission by
768 [perform your edits and commits]
793 If you are not using git to format your patches, you can still include
795 on which your work is based. You should add it either in the cover
798 content, right before your email signature.