Lines Matching refs:patch

38  - If the patch covers files in net/ or drivers/net please follow netdev stable
53 To have the patch automatically included in the stable tree, add the tag
59 in the sign-off area. Once the patch is merged it will be applied to
68 After the patch has been merged to Linus' tree, send an email to
69 stable@vger.kernel.org containing the subject of the patch, the commit ID,
78 Send the patch, after verifying that it follows the above rules, to
84 :ref:`option_2` and :ref:`option_3` are more useful if the patch isn't deemed
87 useful if the patch needs some special handling to apply to an older kernel
90 Note that for :ref:`option_3`, if the patch deviates from the original
91 upstream patch (for example because it had to be backported) this must be very
92 clearly documented and justified in the patch description.
101 Additionally, some patches submitted via Option 1 may have additional patch
139  - The sender will receive an ACK when the patch has been accepted into the
140    queue, or a NAK if the patch is rejected.  This response might take a few
142  - If accepted, the patch will be added to the -stable queue, for review by
151    the patch (unless the submitter is the maintainer of the area) and CC: to
153  - The review committee has 48 hours in which to ACK or NAK the patch.
154  - If the patch is rejected by a member of the committee, or linux-kernel
155    members object to the patch, bringing up issues that the maintainers and
156    members did not realize, the patch will be dropped from the queue.