linux-kernel - [PATCH 03/10] Doc/stable rules: add new cherry-pick logic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1261597963-18323-3-git-send-email-gregkh@suse.de>
Date:	Wed, 23 Dec 2009 11:52:36 -0800
From:	Greg Kroah-Hartman <gregkh@...e.de>
To:	linux-kernel@...r.kernel.org
Cc:	Sebastian Andrzej Siewior <sebastian@...akpoint.cc>,
	Brandon Philips <brandon@...p.org>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: [PATCH 03/10] Doc/stable rules: add new cherry-pick logic

From: Sebastian Andrzej Siewior <sebastian@...akpoint.cc>

- it is possible to submit patches for the stable queue without sending
  them directly stable@...nel.org. If the tag (Cc: stable@...nel.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 <sebastian@...akpoint.cc>
Cc: Brandon Philips <brandon@...p.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>
---
 Documentation/stable_kernel_rules.txt |   24 ++++++++++++++++++++++--
 1 files changed, 22 insertions(+), 2 deletions(-)

diff --git a/Documentation/stable_kernel_rules.txt b/Documentation/stable_kernel_rules.txt
index a452227..5effa5b 100644
--- a/Documentation/stable_kernel_rules.txt
+++ b/Documentation/stable_kernel_rules.txt
@@ -26,13 +26,33 @@ Procedure for submitting patches to the -stable tree:
 
  - Send the patch, after verifying that it follows the above rules, to
    stable@...nel.org.
+ - To have the patch automatically included in the stable tree, add the
+   the tag
+     Cc: stable@...nel.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: <stable@...nel.org> # .32.x: a1f84a3: sched: Check for idle
+     Cc: <stable@...nel.org> # .32.x: 1b9508f: sched: Rate-limit newidle
+     Cc: <stable@...nel.org> # .32.x: fd21073: sched: Fix affinity logic
+     Cc: <stable@...nel.org> # .32.x
+    Signed-off-by: Ingo Molnar <mingo@...e.hu>
+
+   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 stable@...nel.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 security@...nel.org address.
 
-- 
1.6.5.7

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/