Re: [PATCH] stable_kernel_rules: Add clause about specification of kernel versions to patch.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/25/2015 07:05 AM, Greg Kroah-Hartman wrote:
On Mon, Feb 09, 2015 at 03:39:23PM -0800, David Daney wrote:
From: David Daney <david.daney@xxxxxxxxxx>

Signed-off-by: David Daney <david.daney@xxxxxxxxxx>
---
  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@xxxxxxxxxxxxxxx> # 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

This doesn't apply to the tree, what kernel version did you make it
against?  Can you make it against Linus's latest tree and resend it?


I just sent out a new version.

David Daney

--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]