Commit 46cdf871d9970b9252469531f9efd4a17243bb0b
Committed by
Greg Kroah-Hartman
1 parent
2952755ce3
Exists in
master
and in
7 other branches
stable_kernel_rules: fix must already be in mainline
stable_kernel_rules: fix must already be in mainline Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Showing 1 changed file with 5 additions and 2 deletions Side-by-side Diff
Documentation/stable_kernel_rules.txt
... | ... | @@ -16,8 +16,9 @@ |
16 | 16 | race can be exploited is also provided. |
17 | 17 | - It cannot contain any "trivial" fixes in it (spelling changes, |
18 | 18 | whitespace cleanups, etc). |
19 | - - It must be accepted by the relevant subsystem maintainer. | |
20 | 19 | - It must follow the Documentation/SubmittingPatches rules. |
20 | + - It or an equivalent fix must already exist in Linus' tree. Quote the | |
21 | + respective commit ID in Linus' tree in your patch submission to -stable. | |
21 | 22 | |
22 | 23 | |
23 | 24 | Procedure for submitting patches to the -stable tree: |
... | ... | @@ -28,7 +29,9 @@ |
28 | 29 | queue, or a NAK if the patch is rejected. This response might take a few |
29 | 30 | days, according to the developer's schedules. |
30 | 31 | - If accepted, the patch will be added to the -stable queue, for review by |
31 | - other developers. | |
32 | + other developers and by the relevant subsystem maintainer. | |
33 | + - If the stable@kernel.org address is added to a patch, when it goes into | |
34 | + Linus's tree it will automatically be emailed to the stable team. | |
32 | 35 | - Security patches should not be sent to this alias, but instead to the |
33 | 36 | documented security@kernel.org address. |
34 | 37 |