summaryrefslogtreecommitdiff
path: root/Documentation/process/4.Coding.rst
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@s-opensource.com>2016-11-17 13:32:33 +0300
committerJonathan Corbet <corbet@lwn.net>2016-11-19 20:22:04 +0300
commit1dc4bbf0b268246f6202c761016735933b6f0b99 (patch)
tree0bb12a6c59472d8167dbebac4fe6a68023956813 /Documentation/process/4.Coding.rst
parent726d661fea3e3f76d36515c74e4ce58e7789418e (diff)
downloadlinux-1dc4bbf0b268246f6202c761016735933b6f0b99.tar.xz
docs-rst: doc-guide: split the kernel-documentation.rst contents
Having the kernel-documentation at the topmost level doesn't allow generating a separate PDF file for it. Also, makes harder to add extra contents. So, place it on a sub-dir. Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/process/4.Coding.rst')
-rw-r--r--Documentation/process/4.Coding.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/process/4.Coding.rst b/Documentation/process/4.Coding.rst
index 983d628c1112..2a728d898fc5 100644
--- a/Documentation/process/4.Coding.rst
+++ b/Documentation/process/4.Coding.rst
@@ -358,8 +358,8 @@ them, as appropriate, for externally-available functions. Even in areas
which have not been so documented, there is no harm in adding kerneldoc
comments for the future; indeed, this can be a useful activity for
beginning kernel developers. The format of these comments, along with some
-information on how to create kerneldoc templates can be found in the file
-Documentation/kernel-documentation.rst.
+information on how to create kerneldoc templates can be found at
+:ref:`Documentation/doc-guide/ <doc_guide>`.
Anybody who reads through a significant amount of existing kernel code will
note that, often, comments are most notable by their absence. Once again,