diff options
| author | Luke Dashjr <luke@dashjr.org> | 2015-05-14 18:58:01 +0000 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2015-05-14 15:34:52 -0400 |
| commit | 8cda4c3ad480a974324532b6dacc67b9c1deb207 (patch) | |
| tree | 0d6111f1feb6e4eeb2a6acdd1bf888b05ce99e48 | |
| parent | 8547aa131495b081ef3e5ada8bc726251e23d2e0 (diff) | |
SubmittingPatches: Clarify requirements for patches directed toward stable
I misunderstood this section as simply asking me to add an email Cc, and
was unaware of the existence of Documentation/stable_kernel_rules.txt.
Hopefully this clarification will help save maintainers and new/rare
submitters time in the future.
Signed-off-by: Luke Dashjr <luke-jr+git@utopios.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
| -rw-r--r-- | Documentation/SubmittingPatches | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index b03a832a08e2..27e7e5edeca8 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -299,7 +299,9 @@ toward the stable maintainers by putting a line like this: Cc: stable@vger.kernel.org -into your patch. +into the sign-off area of your patch (note, NOT an email recipient). You +should also read Documentation/stable_kernel_rules.txt in addition to this +file. Note, however, that some subsystem maintainers want to come to their own conclusions on which patches should go to the stable trees. The networking |