/security/

entation/SubmittingDrivers Documentation/SubmittingPatches Documentation/development-process/development-process.rst Documentation/stable_kernel_rules.txt Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Documentation/HOWTO: add cross-references to other documents 2016-09-21T00:41:04Z Mauro Carvalho Chehab mchehab@s-opensource.com 2016-09-19T11:07:56Z urn:sha1:609d99a3b72e3964279a068868a212553087eb22 Add cross references for the documents mentioned at HOWTO and are under the Documentation/ directory, using the ReST notation. It should be noticed that HOWTO also mentions the /README file. We opted to not touch it, for now, as making it build on Sphinx would require it to be moved to a Documentation/foo directory. Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Documentation/stable_kernel_rules.txt: convert it to ReST markup 2016-09-21T00:38:51Z Mauro Carvalho Chehab mchehab@s-opensource.com 2016-09-19T11:07:51Z urn:sha1:5fe270a47ebf594a3c538a3c44e9a20a96015b19 - use ReST markups for section headers; - add cross-references to the options; - mark code blocks; - a few minor changes to make Sphinx happy. Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net> stable_kernel_rules.txt: Remove extra space after Cc: 2015-11-20T23:54:57Z Richard Weinberger richard@nod.at 2015-11-18T08:58:38Z urn:sha1:f902493a681659998856cabcfefa862ddaec952c Fixes the checkpatch.pl warning: "WARNING: Use a single space after Cc:" Very lazy hackers just copy&paste the stable tag from this document. As it contains an extra space, checkpatch.pl will not like the resulting patch... Signed-off-by: Richard Weinberger <richard@nod.at> Signed-off-by: Jonathan Corbet <corbet@lwn.net> stable: Update documentation to clarify preferred procedure 2015-05-22T15:38:56Z Christoffer Dall christoffer.dall@linaro.org 2015-05-13T20:01:07Z urn:sha1:bde1b29420d71a17d87332db8e20229f251d6c14 Clearly specify that "Cc: stable@vger.kernel.org" is strongly preferred so that developers understand that the other options should only be used when absolutely required. Also specify how upstream commit ids should be referenced in patches submitted directly to stable (I gathered this from looking at the stable archives), and specify that any modified patches for stable should be clearly documented in the patch description. Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net> stable_kernel_rules: Add clause about specification of kernel versions to patch. 2015-03-26T22:52:24Z David Daney david.daney@cavium.com 2015-03-26T17:09:08Z urn:sha1:fdc81b7910ad5153bf257e5f7861be71f75a02ef Signed-off-by: David Daney <david.daney@cavium.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> stable_kernel_rules: reorganize and update submission options 2015-01-12T13:04:12Z Brian Norris computersforpeace@gmail.com 2014-12-18T22:55:53Z urn:sha1:5de61e7aa1ba9ac3c7edbea375da2bc8eb1a89ae The current organization of Documentation/stable_kernel_rules.txt doesn't clearly differentiate the mutually exclusive options for submission to the -stable review process. As I understand it, patches are not actually required to be mailed directly to stable@vger.kernel.org, but the instructions do not make this clear. Also, there are some established processes that are not listed -- specifically, what I call Option 2 below. This patch updates and reorganizes a bit, to make things clearer. Signed-off-by: Brian Norris <computersforpeace@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>