On Fri, Jun 27, 2025 at 12:06 PM Randy Dunlap <rdunlap@xxxxxxxxxxxxx> wrote:
>
> Add "alldefconfig" to the explanation of the KCONFIG_ALLCONFIG
> environment variable usage so that all targets that use KCONFIG_ALLCONFIG
> are listed.
>
> Signed-off-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
> Cc: Jonathan Corbet <corbet@xxxxxxx>
> Cc: linux-doc@xxxxxxxxxxxxxxx
> Cc: Masahiro Yamada <masahiroy@xxxxxxxxxx>
> Cc: Nathan Chancellor <nathan@xxxxxxxxxx>
> Cc: Nicolas Schier <nicolas.schier@xxxxxxxxx>
> Cc: linux-kbuild@xxxxxxxxxxxxxxx
> ---
Applied to linux-kbuild.
Thanks.
> Documentation/kbuild/kconfig.rst | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> --- lnx-616-rc3.orig/Documentation/kbuild/kconfig.rst
> +++ lnx-616-rc3/Documentation/kbuild/kconfig.rst
> @@ -67,12 +67,12 @@ Environment variables for ``*config``:
> with its value when saving the configuration, instead of using the
> default, ``CONFIG_``.
>
> -Environment variables for ``{allyes/allmod/allno/rand}config``:
> +Environment variables for ``{allyes/allmod/allno/alldef/rand}config``:
>
> ``KCONFIG_ALLCONFIG``
> - The allyesconfig/allmodconfig/allnoconfig/randconfig variants can also
> - use the environment variable KCONFIG_ALLCONFIG as a flag or a filename
> - that contains config symbols that the user requires to be set to a
> + The allyesconfig/allmodconfig/alldefconfig/allnoconfig/randconfig variants
> + can also use the environment variable KCONFIG_ALLCONFIG as a flag or a
> + filename that contains config symbols that the user requires to be set to a
> specific value. If KCONFIG_ALLCONFIG is used without a filename where
> KCONFIG_ALLCONFIG == "" or KCONFIG_ALLCONFIG == "1", ``make *config``
> checks for a file named "all{yes/mod/no/def/random}.config"
--
Best Regards
Masahiro Yamada
