[PATCH 3/3] Documentation: kernel-hacking: Convert internal links

Bagas Sanjaya
2025-12-23T03:53:11Z

Convert internal cross-references in "Putting Your Stuff in the kernel"
section from inline code to internal links.

Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/kernel-hacking/hacking.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/kernel-hacking/hacking.rst b/Documentation/kernel-hacking/hacking.rst
index 1d120ff80f956c..ef527bdc5f8daa 100644
--- a/Documentation/kernel-hacking/hacking.rst
+++ b/Documentation/kernel-hacking/hacking.rst
@@ -735,7 +735,7 @@ make a neat patch, there's administrative work to be done:
- Usually you want a configuration option for your kernel hack. Edit
``Kconfig`` in the appropriate directory. The Config language is
simple to use by cut and paste, and there's complete documentation in
- ``Documentation/kbuild/kconfig-language.rst``.
+ Documentation/kbuild/kconfig-language.rst.

In your description of the option, make sure you address both the
expert user and the user who knows nothing about your feature.
@@ -745,7 +745,7 @@ make a neat patch, there's administrative work to be done:

- Edit the ``Makefile``: the CONFIG variables are exported here so you
can usually just add a "obj-$(CONFIG_xxx) += xxx.o" line. The syntax
- is documented in ``Documentation/kbuild/makefiles.rst``.
+ is documented in Documentation/kbuild/makefiles.rst.

- Put yourself in ``CREDITS`` if you consider what you've done
noteworthy, usually beyond a single file (your name should be at the
@@ -754,7 +754,7 @@ make a neat patch, there's administrative work to be done:
it implies a more-than-passing commitment to some part of the code.

- Finally, don't forget to read
- ``Documentation/process/submitting-patches.rst``
+ Documentation/process/submitting-patches.rst.

Kernel Cantrips
===============