On Mon, Feb 09, 2015 at 03:39:23PM -0800, David Daney wrote: > From: David Daney <[email protected]> > Better if it is added in commit message: how to determine kernel version for a given commit id.
> Signed-off-by: David Daney <[email protected]> > --- > 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: <[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: > -- > 1.7.11.7 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
