Lines Matching refs:that

17 completely "ready."  For simple patches, that is not a problem.  If the
21 that interested developers can catch up with your work at any time.
27 with the idea that they can help you drive the work in the right direction.
35  - Test the code to the extent that you can.  Make use of the kernel's
36    debugging tools, ensure that the kernel will build with all reasonable
47  - Be sure that you have the right to post the code.  If this work was done
76 out how to do it in the way that the community expects.  There are a few
96    good chance that it will be passed over and the important fix will be
113    patches, but to leave that infrastructure unused until the final patch
115    avoided if possible; if that series adds regressions, bisection will
118    code should make that code active immediately.
130 that end, each patch will be composed of the following:
138    scope of the patch; it is the line that will show up in the "short form"
155 bear in mind that a number of different people will be reading your words.
164 To that end, the summary line should describe the effects of and motivation
170 specific log or compiler output, include that output to help others
175 be reading your changelog, the better that changelog (and the kernel as a
199  - Signed-off-by: this is a developer's certification that he or she has
206    maintainer of the relevant code) that the patch is appropriate for
209  - Tested-by: states that the named person has tested the patch and found
233  - Are you sure that your mailer will not corrupt the patches?  Patches
237    to yourself and convince yourself that it shows up intact.
244    comes up with.  Please bear in mind that checkpatch.pl, while being the
250 attachments; that makes it much harder for reviewers to quote sections of
256 people to err on the side of sending too many copies; don't assume that the
276    the patch itself; that will cause the stable team to get a notification
282 them, things are not normally done that way.  Linus is busy, and there are
284 you will be wanting that maintainer to merge your patches.  If there is no
298 followed though; if you use it, remember that information in the
300 that the patches, themselves, have complete changelog information.
303 sent as a reply to the first part so that they all thread together at the