[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <9a819ea3d39cacdf6917de0b8570b59b66bb38d8.1473893776.git.mchehab@s-opensource.com>
Date: Wed, 14 Sep 2016 20:06:01 -0300
From: Mauro Carvalho Chehab <mchehab@...pensource.com>
To: Linux Doc Mailing List <linux-doc@...r.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@...pensource.com>,
Mauro Carvalho Chehab <mchehab@...radead.org>,
Jonathan Corbet <corbet@....net>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Richard Weinberger <richard@....at>,
Markus Heiser <markus.heiser@...marit.de>,
Jani Nikula <jani.nikula@...ux.intel.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: [PATCH 16/17] stable_kernel_rules.rst: Add cross-references to other ReST files
Add two references for files that were already converted to ReST.
Signed-off-by: Mauro Carvalho Chehab <mchehab@...pensource.com>
---
Documentation/development-process/stable_kernel_rules.rst | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/Documentation/development-process/stable_kernel_rules.rst b/Documentation/development-process/stable_kernel_rules.rst
index 533be00260e6..daa1073b65df 100644
--- a/Documentation/development-process/stable_kernel_rules.rst
+++ b/Documentation/development-process/stable_kernel_rules.rst
@@ -26,7 +26,9 @@ Rules on what kind of patches are accepted, and which ones are not, into the
race can be exploited is also provided.
- It cannot contain any "trivial" fixes in it (spelling changes,
whitespace cleanups, etc).
- - It must follow the Documentation/development-process/SubmittingPatches.rst rules.
+ - It must follow the
+ :ref:`Documentation/development-process/SubmittingPatches.rst <submittingpatches>`
+ rules.
- It or an equivalent fix must already exist in Linus' tree (upstream).
@@ -37,7 +39,8 @@ Procedure for submitting patches to the -stable tree
submission guidelines as described in
Documentation/networking/netdev-FAQ.txt
- Security patches should not be handled (solely) by the -stable review
- process but should follow the procedures in Documentation/development-process/SecurityBugs.rst.
+ process but should follow the procedures in
+ :ref:`Documentation/development-process/SecurityBugs.rst <securitybugs>`.
For all other submissions, choose one of the following procedures
-----------------------------------------------------------------
--
2.7.4
Powered by blists - more mailing lists