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
79 Once the patch is mainlined it will be applied to the stable tree without
85 * Specify any additional patch prerequisites for cherry picking::
100   Note that for a patch series, you do not have to list as prerequisites the
102   patch series::
130     Cc: <[email protected]> # see patch description, needs adjustments for <= 6.3
143 If the patch already has been merged to mainline, send an email to
144 [email protected] containing the subject of the patch, the commit ID,
153 Send the patch, after verifying that it follows the above rules, to
164 If the submitted patch deviates from the original upstream patch (for example
166 documented and justified in the patch description.
172 The sender will receive an ACK when the patch has been accepted into the
173 queue, or a NAK if the patch is rejected.  This response might take a few
176 If accepted, the patch will be added to the -stable queue, for review by other
185   the patch (unless the submitter is the maintainer of the area) and CC: to
187 - The review committee has 48 hours in which to ACK or NAK the patch.
188 - If the patch is rejected by a member of the committee, or linux-kernel
189   members object to the patch, bringing up issues that the maintainers and
190   members did not realize, the patch will be dropped from the queue.