Skip to contentSkip to conversation

stable_kernel_rules: Add clause about specification of kernel versions to patch.

PATCH Hillf Danton 2 participants 2 messages Mar 26, 2015

lore
Share & tools
lore
#0 lore raw
Quoted 2 lines · David Daney

From: David Daney <[email protected]>

Better if it is added in commit message:
how to determine kernel version for a given commit id.

Quoted 28 lines
---
 Documentation/stable_kernel_rules.txt | 10 ++++++++++
 1 file changed, 10 insertions(+)
Documentation/stable_kernel_rules.txt +10 -0
index aee73e7..82c097a 100644
@@ -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:  <[email protected]> # 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:
Signature · 1 line
1.7.11.7
#1 lore raw
Quoted 6 lines · Hillf Danton
Quoted 2 lines · David Daney

From: David Daney <[email protected]>

Better if it is added in commit message:
how to determine kernel version for a given commit id.

Perhaps. I think that if you wrote and submitted such a patch, the maintainers would probably merge it.

David Daney