From 7b5409b811ad41373834b888bf1a1e0ec2187cd8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Carlos=20S=C3=A1nchez=20de=20La=20Lama?= Date: Wed, 28 May 2025 20:15:24 +0200 Subject: [PATCH] ref-manual: clarify KCONFIG_MODE default behaviour MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit KCONFIG_MODE defaults to 'allnoconfig' when not set, regardless of whether KBUILD_DEFCONFIG points to an in-tree or a meta-layer defconfig. (From yocto-docs rev: f374b9c426f6c10710e011a4ad660231ee26efb8) Signed-off-by: Carlos Sánchez de La Lama Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie --- documentation/ref-manual/variables.rst | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst index 9768d8f5b8..5c18b852d1 100644 --- a/documentation/ref-manual/variables.rst +++ b/documentation/ref-manual/variables.rst @@ -5036,15 +5036,8 @@ system and gives an overview of their function and contents. options not explicitly specified will be disabled in the kernel config. - In case :term:`KCONFIG_MODE` is not set the behaviour will depend on where - the ``defconfig`` file is coming from. An "in-tree" ``defconfig`` file - will be handled in ``alldefconfig`` mode, a ``defconfig`` file placed - in ``${WORKDIR}`` through a meta-layer will be handled in - ``allnoconfig`` mode. - - An "in-tree" ``defconfig`` file can be selected via the - :term:`KBUILD_DEFCONFIG` variable. :term:`KCONFIG_MODE` does not need to - be explicitly set. + In case :term:`KCONFIG_MODE` is not set the ``defconfig`` file + will be handled in ``allnoconfig`` mode. A ``defconfig`` file compatible with ``allnoconfig`` mode can be generated by copying the ``.config`` file from a working Linux kernel