redonkable
/
alistair23-linux
1
0
Fork 0
Code Releases Activity

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>
hifive-unleashed-5.1
Luke Dashjr 2015-05-14 18:58:01 +00:00 committed by Jonathan Corbet
parent 8547aa1314
commit 8cda4c3ad4
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/SubmittingPatches
View File

@ -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