| Message ID | 20250528181524.2797025-1-csanchezdll@gmail.com |
|---|---|
| State | New |
| Headers | show |
| Series | ref-manual: clarify KCONFIG_MODE default behaviour | expand |
Hi, @Bruce (now in To) I see this was agreed on on the ML, can you provide feedback on this patch maybe? Thanks! This patch seems reasonable to me but would rather have a second opinion from the maintainer of the recipe/class :) Cheers, Quentin On 5/28/25 8:15 PM, Carlos Sánchez de La Lama via lists.yoctoproject.org wrote: > [You don't often get email from csanchezdll=gmail.com@lists.yoctoproject.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] > > KCONFIG_MODE defaults to 'allnoconfig' when not set, regardless of whether > KBUILD_DEFCONFIG points to an in-tree or a meta-layer defconfig. > > Signed-off-by: Carlos Sánchez de La Lama <csanchezdll@gmail.com> > > --- > > Previous discussion: > https://lore.kernel.org/yocto/CA+KcR8ARBUj8PTcvA=rx-yob=WHYcS2gUnGX2aROOjy6bZGqWw@mail.gmail.com/ > > 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 c697bdbbb..da274f3fe 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 > > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#6946): https://lists.yoctoproject.org/g/docs/message/6946 > Mute This Topic: https://lists.yoctoproject.org/mt/113349230/6293953 > Group Owner: docs+owner@lists.yoctoproject.org > Unsubscribe: https://lists.yoctoproject.org/g/docs/unsub [quentin.schulz@cherry.de] > -=-=-=-=-=-=-=-=-=-=-=- >
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst index c697bdbbb..da274f3fe 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
KCONFIG_MODE defaults to 'allnoconfig' when not set, regardless of whether KBUILD_DEFCONFIG points to an in-tree or a meta-layer defconfig. Signed-off-by: Carlos Sánchez de La Lama <csanchezdll@gmail.com> --- Previous discussion: https://lore.kernel.org/yocto/CA+KcR8ARBUj8PTcvA=rx-yob=WHYcS2gUnGX2aROOjy6bZGqWw@mail.gmail.com/ documentation/ref-manual/variables.rst | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-)