stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Daney <ddaney.cavm@gmail.com>
To: linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org
Cc: David Daney <david.daney@cavium.com>
Subject: [PATCH] stable_kernel_rules: Add clause about specification of kernel versions to patch.
Date: Mon,  9 Feb 2015 15:39:23 -0800	[thread overview]
Message-ID: <1423525163-22145-1-git-send-email-ddaney.cavm@gmail.com> (raw)

From: David Daney <david.daney@cavium.com>

Signed-off-by: David Daney <david.daney@cavium.com>
---
 Documentation/stable_kernel_rules.txt | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/Documentation/stable_kernel_rules.txt b/Documentation/stable_kernel_rules.txt
index aee73e7..82c097a 100644
--- a/Documentation/stable_kernel_rules.txt
+++ b/Documentation/stable_kernel_rules.txt
@@ -41,6 +41,16 @@ Procedure for submitting patches to the -stable tree:
    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.
+ - The kernel versions, to which the patch should be applied, can be
+   specified in the following format in the sign-off area:
+
+     Cc:  <stable@vger.kernel.org> # 3.3.x
+
+   The tag has the meaning of:
+     git cherry-pick <this commit>
+
+   For each "-stable" tree starting with the specified version.
+
  - If the patch requires other patches as prerequisites which can be
    cherry-picked, then this can be specified in the following format in
    the sign-off area:
-- 
1.7.11.7


             reply	other threads:[~2015-02-09 23:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 23:39 David Daney [this message]
2015-02-09 23:59 ` [PATCH] stable_kernel_rules: Add clause about specification of kernel versions to patch Greg Kroah-Hartman
2015-03-25 14:05 ` Greg Kroah-Hartman
2015-03-26 16:45   ` David Daney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1423525163-22145-1-git-send-email-ddaney.cavm@gmail.com \
    --to=ddaney.cavm@gmail.com \
    --cc=david.daney@cavium.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).