Lines Matching full:patch

45  1. Add a 'stable tag' to the description of a patch you then submit for
47  2. Ask the stable team to pick up a patch already mainlined.
48  3. Submit a patch to the stable team that is equivalent to a change already
56 options for cases where a mainlined patch needs adjustments to apply in older
70 To have a patch you submit for mainline inclusion later automatically picked up
77 in the sign-off area. Once the patch is mainlined it will be applied to the
84  * To specify any additional patch prerequisites for cherry picking use the
104    Note that for a patch series, you do not have to list as prerequisites the
106    patch series:
146      Cc: <stable@vger.kernel.org> # see patch description, needs adjustments for <= 6.3
153 If the patch already has been merged to mainline, send an email to
154 stable@vger.kernel.org containing the subject of the patch, the commit ID,
163 Send the patch, after verifying that it follows the above rules, to
178 If the submitted patch deviates from the original upstream patch (for example
180 documented and justified in the patch description.
186 The sender will receive an ACK when the patch has been accepted into the
187 queue, or a NAK if the patch is rejected.  This response might take a few
190 If accepted, the patch will be added to the -stable queue, for review by other
199    the patch (unless the submitter is the maintainer of the area) and CC: to
201  - The review committee has 48 hours in which to ACK or NAK the patch.
202  - If the patch is rejected by a member of the committee, or linux-kernel
203    members object to the patch, bringing up issues that the maintainers and
204    members did not realize, the patch will be dropped from the queue.