|author||Sebastian Andrzej Siewior <email@example.com>||2009-12-06 12:24:31 +0100|
|committer||Greg Kroah-Hartman <firstname.lastname@example.org>||2009-12-23 11:23:43 -0800|
Doc/stable rules: add new cherry-pick logic
- it is possible to submit patches for the stable queue without sending them directly email@example.com. If the tag (Cc: firstname.lastname@example.org) is available in the sign-off area than hpa's script will filter them into the stable mailbox once it hits Linus' tree. - Patches which require others to be applied first can be also specified. This was discussued in http://lkml.org/lkml/2009/11/9/474 Signed-off-by: Sebastian Andrzej Siewior <email@example.com> Cc: Brandon Philips <firstname.lastname@example.org> Signed-off-by: Greg Kroah-Hartman <email@example.com>
Diffstat (limited to 'Documentation')
1 files changed, 22 insertions, 2 deletions
diff --git a/Documentation/stable_kernel_rules.txt b/Documentation/stable_kernel_rules.txt
index a452227361b1..5effa5bd993b 100644
@@ -26,13 +26,33 @@ Procedure for submitting patches to the -stable tree:
- Send the patch, after verifying that it follows the above rules, to
+ - To have the patch automatically included in the stable tree, add the
+ the tag
+ Cc: firstname.lastname@example.org
+ in the sign-off area. Once the patch is merged it will be applied to
+ the stable tree without anything else needing to be done by the author
+ or subsystem maintainer.
+ - If the patch requires other patches as prerequisites which can be
+ cherry-picked than this can be specified in the following format in
+ the sign-off area:
+ Cc: <email@example.com> # .32.x: a1f84a3: sched: Check for idle
+ Cc: <firstname.lastname@example.org> # .32.x: 1b9508f: sched: Rate-limit newidle
+ Cc: <email@example.com> # .32.x: fd21073: sched: Fix affinity logic
+ Cc: <firstname.lastname@example.org> # .32.x
+ Signed-off-by: Ingo Molnar <email@example.com>
+ The tag sequence has the meaning of:
+ git cherry-pick a1f84a3
+ git cherry-pick 1b9508f
+ git cherry-pick fd21073
+ git cherry-pick <this commit>
- The sender will receive an ACK when the patch has been accepted into the
queue, or a NAK if the patch is rejected. This response might take a few
days, according to the developer's schedules.
- If accepted, the patch will be added to the -stable queue, for review by
other developers and by the relevant subsystem maintainer.
- - If the firstname.lastname@example.org address is added to a patch, when it goes into
- Linus's tree it will automatically be emailed to the stable team.
- Security patches should not be sent to this alias, but instead to the
documented email@example.com address.