From 043592a585ef6dab73e285985b381a11b91570a8 Mon Sep 17 00:00:00 2001 From: Nicolas Dechesne Date: Thu, 19 Nov 2020 10:58:28 +0100 Subject: kernel-dev: replace labels with references to section title (From yocto-docs rev: 0a0a5d3ad6c2e551db0d43b1e76b8c459c347dc5) Signed-off-by: Nicolas Dechesne Signed-off-by: Richard Purdie --- documentation/kernel-dev/kernel-dev-advanced.rst | 4 ++-- documentation/kernel-dev/kernel-dev-intro.rst | 8 ++++---- 2 files changed, 6 insertions(+), 6 deletions(-) (limited to 'documentation/kernel-dev') diff --git a/documentation/kernel-dev/kernel-dev-advanced.rst b/documentation/kernel-dev/kernel-dev-advanced.rst index 444037c3a7..b1537ccbe2 100644 --- a/documentation/kernel-dev/kernel-dev-advanced.rst +++ b/documentation/kernel-dev/kernel-dev-advanced.rst @@ -245,7 +245,7 @@ two files: ``smp.scc`` and ``smp.cfg``. You can find these files in the CONFIG_X86_BIGSMP=y You can find general information on configuration -fragment files in the ":ref:`creating-config-fragments`" section. +fragment files in the ":ref:`kernel-dev/kernel-dev-common:creating configuration fragments`" section. Within the ``smp.scc`` file, the :term:`KFEATURE_DESCRIPTION` @@ -559,7 +559,7 @@ You can see that in the BeagleBone example with the following: include beaglebone.scc For information on how to break a complete ``.config`` file into the various -configuration fragments, see the ":ref:`creating-config-fragments`" section. +configuration fragments, see the ":ref:`kernel-dev/kernel-dev-common:creating configuration fragments`" section. Finally, if you have any configurations specific to the hardware that are not in a ``*.scc`` file, you can include them as follows: diff --git a/documentation/kernel-dev/kernel-dev-intro.rst b/documentation/kernel-dev/kernel-dev-intro.rst index 5679a0ab80..971420b228 100644 --- a/documentation/kernel-dev/kernel-dev-intro.rst +++ b/documentation/kernel-dev/kernel-dev-intro.rst @@ -28,8 +28,8 @@ newly-supported platforms. Previous recipes in the release are refreshed and supported for at least one additional Yocto Project release. As they align, these previous releases are updated to include the latest from the Long Term Support Initiative (LTSI) project. You can learn more -about Yocto Linux kernels and LTSI in the ":ref:`Yocto Project Kernel -Development and Maintenance `" section. +about Yocto Linux kernels and LTSI in the +":ref:`kernel-dev/kernel-dev-concepts-appx:yocto project kernel development and maintenance`" section. Also included is a Yocto Linux kernel development recipe (``linux-yocto-dev.bb``) should you want to work with the very latest in @@ -38,7 +38,7 @@ upstream Yocto Linux kernel development and kernel Metadata development. .. note:: For more on Yocto Linux kernels, see the - ":ref:`Yocto Project Kernel Development and Maintenance `" + ":ref:`kernel-dev/kernel-dev-concepts-appx:yocto project kernel development and maintenance`" section. The Yocto Project also provides a powerful set of kernel tools for @@ -167,7 +167,7 @@ general information and references for further information. ``menuconfig`` and you have saved them, you can directly compare the resulting ``.config`` file against an existing original and gather those changes into a - :ref:`configuration fragment file ` to be + :ref:`configuration fragment file ` to be referenced from within the kernel's ``.bbappend`` file. Additionally, if you are working in a BSP layer and need to modify -- cgit v1.2.3-54-g00ecf