summaryrefslogtreecommitdiff
path: root/Documentation/process/howto.rst
diff options
context:
space:
mode:
authorFederico Vaga <federico.vaga@vaga.pv.it>2018-11-21 03:35:19 +0300
committerJonathan Corbet <corbet@lwn.net>2018-12-06 20:21:19 +0300
commitf77af637f29da49193283e883a9b18406fb45d3d (patch)
tree44602d9f6cc417dda0432d4d5171e63162204f6e /Documentation/process/howto.rst
parent2f7e6f6bf0d5fda265e403423921588cda7ce16e (diff)
downloadlinux-f77af637f29da49193283e883a9b18406fb45d3d.tar.xz
doc:process: add links where missing
Some documents are refering to others without links. With this patch I add those missing links. This patch affects only documents under process/ and labels where necessary. Signed-off-by: Federico Vaga <federico.vaga@vaga.pv.it> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/process/howto.rst')
-rw-r--r--Documentation/process/howto.rst11
1 files changed, 6 insertions, 5 deletions
diff --git a/Documentation/process/howto.rst b/Documentation/process/howto.rst
index a4a9f9eb0dd8..58b2f46c4f98 100644
--- a/Documentation/process/howto.rst
+++ b/Documentation/process/howto.rst
@@ -298,9 +298,9 @@ two weeks, but it can be longer if there are no pressing problems. A
security-related problem, instead, can cause a release to happen almost
instantly.
-The file Documentation/process/stable-kernel-rules.rst in the kernel tree
-documents what kinds of changes are acceptable for the -stable tree, and
-how the release process works.
+The file :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
+in the kernel tree documents what kinds of changes are acceptable for
+the -stable tree, and how the release process works.
4.x -git patches
~~~~~~~~~~~~~~~~
@@ -360,7 +360,8 @@ tool. For details on how to use the kernel bugzilla, please see:
https://bugzilla.kernel.org/page.cgi?id=faq.html
-The file admin-guide/reporting-bugs.rst in the main kernel source directory has a good
+The file :ref:`admin-guide/reporting-bugs.rst <reportingbugs>`
+in the main kernel source directory has a good
template for how to report a possible kernel bug, and details what kind
of information is needed by the kernel developers to help track down the
problem.
@@ -426,7 +427,7 @@ add your statements between the individual quoted sections instead of
writing at the top of the mail.
If you add patches to your mail, make sure they are plain readable text
-as stated in Documentation/process/submitting-patches.rst.
+as stated in :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`.
Kernel developers don't want to deal with
attachments or compressed patches; they may want to comment on
individual lines of your patch, which works only that way. Make sure you