Add two references for files that were already converted to ReST.
Signed-off-by: Mauro Carvalho Chehab <mche...@s-opensource.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
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
