user/sven/linux.git/Documentation/stable_kernel_rules.txt, branch v4.9.20

docs-rst: add inter-document cross references

2016-09-21T21:43:09Z

Add cross references for the development process documents that were converted to ReST: Documentation/SubmitChecklist Documentation/SubmittingDrivers Documentation/SubmittingPatches Documentation/development-process/development-process.rst Documentation/stable_kernel_rules.txt Signed-off-by: Mauro Carvalho Chehab Acked-by: Greg Kroah-Hartman Signed-off-by: Jonathan Corbet

Documentation/HOWTO: add cross-references to other documents

2016-09-21T00:41:04Z

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 Acked-by: Greg Kroah-Hartman Signed-off-by: Jonathan Corbet

Documentation/stable_kernel_rules.txt: convert it to ReST markup

2016-09-21T00:38:51Z

- 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 Acked-by: Greg Kroah-Hartman Signed-off-by: Jonathan Corbet

stable_kernel_rules.txt: Remove extra space after Cc:

2015-11-20T23:54:57Z

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 Signed-off-by: Jonathan Corbet

stable: Update documentation to clarify preferred procedure

2015-05-22T15:38:56Z

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 Signed-off-by: Jonathan Corbet

stable_kernel_rules: Add clause about specification of kernel versions to patch.

2015-03-26T22:52:24Z

Signed-off-by: David Daney Signed-off-by: Greg Kroah-Hartman

stable_kernel_rules: reorganize and update submission options

2015-01-12T13:04:12Z

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 Signed-off-by: Greg Kroah-Hartman

stable_kernel_rules: Add pointer to netdev-FAQ for network patches

2014-07-09T22:54:27Z

Stable_kernel_rules should point submitters of network stable patches to the netdev_FAQ.txt as requests for stable network patches should go to netdev first. Signed-off-by: Dave Chiluk Cc: stable Signed-off-by: Greg Kroah-Hartman

stable_kernel_rules: spelling/word usage

2014-04-16T21:13:26Z

"than" should be "then" Signed-off-by: Brian Norris Signed-off-by: Greg Kroah-Hartman

stable: Allow merging of backports for serious user-visible performance issues

2012-06-25T18:25:00Z

Distribution kernel maintainers routinely backport fixes for users that were deemed important but not "something critical" as defined by the rules. To users of these kernels they are very serious and failing to fix them reduces the value of -stable. The problem is that the patches fixing these issues are often subtle and prone to regressions in other ways and need greater care and attention. To combat this, these "serious" backports should have a higher barrier to entry. This patch relaxes the rules to allow a distribution maintainer to merge to -stable a backported patch or small series that fixes a "serious" user-visible performance issue. They should include additional information on the user-visible bug affected and a link to the bugzilla entry if available. The same rules about the patch being already in mainline still apply. Signed-off-by: Mel Gorman Cc: stable Signed-off-by: Greg Kroah-Hartman