Lines Matching refs:patch

38  - If the patch covers files in net/ or drivers/net please follow netdev stable
43    to ensure the requested patch is not already queued up.
56 To have the patch automatically included in the stable tree, add the tag
62 in the sign-off area. Once the patch is merged it will be applied to
71 After the patch has been merged to Linus' tree, send an email to
72 stable@vger.kernel.org containing the subject of the patch, the commit ID,
81 Send the patch, after verifying that it follows the above rules, to
87 :ref:`option_2` and :ref:`option_3` are more useful if the patch isn't deemed
90 useful if the patch needs some special handling to apply to an older kernel
93 Note that for :ref:`option_3`, if the patch deviates from the original
94 upstream patch (for example because it had to be backported) this must be very
95 clearly documented and justified in the patch description.
105 patch prerequisites which can be cherry-picked. This can be specified in the
142  - The sender will receive an ACK when the patch has been accepted into the
143    queue, or a NAK if the patch is rejected.  This response might take a few
145  - If accepted, the patch will be added to the -stable queue, for review by
154    the patch (unless the submitter is the maintainer of the area) and CC: to
156  - The review committee has 48 hours in which to ACK or NAK the patch.
157  - If the patch is rejected by a member of the committee, or linux-kernel
158    members object to the patch, bringing up issues that the maintainers and
159    members did not realize, the patch will be dropped from the queue.