Lines Matching refs:the

3 Rules on what kind of patches are accepted, and which ones are not, into the
20    exists and additional information on the user-visible impact.
22  - No "theoretical race condition" issues, unless an explanation of how the
26  - It must follow the Documentation/SubmittingPatches rules.
30 Procedure for submitting patches to the -stable tree:
32  - If the patch covers files in net/ or drivers/net please follow netdev stable
35  - Security patches should not be handled (solely) by the -stable review
36    process but should follow the procedures in Documentation/SecurityBugs.
38 For all other submissions, choose one of the following procedures:
42    To have the patch automatically included in the stable tree, add the tag
44    in the sign-off area. Once the patch is merged it will be applied to
45    the stable tree without anything else needing to be done by the author
50    After the patch has been merged to Linus' tree, send an email to
51    stable@vger.kernel.org containing the subject of the patch, the commit ID,
57    Send the patch, after verifying that it follows the above rules, to
58    stable@vger.kernel.org.  You must note the upstream commit ID in the
59    changelog of your submission, as well as the kernel version you wish
62 Option 1 is *strongly* preferred, is the easiest and most common.  Options 2 and
63 3 are more useful if the patch isn't deemed worthy at the time it is applied to
65 first).  Option 3 is especially useful if the patch needs some special handling
66 to apply to an older kernel (e.g., if API's have changed in the meantime).
68 Note that for Option 3, if the patch deviates from the original upstream patch
70 documented and justified in the patch description.
72 The upstream commit ID must be specified with a separate line above the commit
78 prerequisites which can be cherry-picked. This can be specified in the following
79 format in the sign-off area:
87    The tag sequence has the meaning of:
94 specified in the following format in the sign-off area:
98    The tag has the meaning of:
101    For each "-stable" tree starting with the specified version.
103 Following the submission:
105  - The sender will receive an ACK when the patch has been accepted into the
106    queue, or a NAK if the patch is rejected.  This response might take a few
107    days, according to the developer's schedules.
108  - If accepted, the patch will be added to the -stable queue, for review by
109    other developers and by the relevant subsystem maintainer.
114  - When the -stable maintainers decide for a review cycle, the patches will be
115    sent to the review committee, and the maintainer of the affected area of
116    the patch (unless the submitter is the maintainer of the area) and CC: to
117    the linux-kernel mailing list.
118  - The review committee has 48 hours in which to ACK or NAK the patch.
119  - If the patch is rejected by a member of the committee, or linux-kernel
120    members object to the patch, bringing up issues that the maintainers and
121    members did not realize, the patch will be dropped from the queue.
122  - At the end of the review cycle, the ACKed patches will be added to the
124  - Security patches will be accepted into the -stable tree directly from the
125    security kernel team, and not go through the normal review cycle.
126    Contact the kernel security team for more details on this procedure.