[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240229021010.GM11972@google.com>
Date: Thu, 29 Feb 2024 11:10:10 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2] kconfig: add some Kconfig env variables to make help
On (24/02/29 11:03), Masahiro Yamada wrote:
> > > > > +++ b/scripts/kconfig/Makefile
> > > > > @@ -158,6 +158,10 @@ help:
> > > > > if help=$$(grep -m1 '^# Help: ' $(f)); then \
> > > > > printf ' %-25s - %s\n' '$(notdir $(f))' "$${help#*: }"; \
> > > > > fi;)
> > > > > + @echo ''
> > > > > + @echo 'Configuration environment variables:'
> > > > > + @echo ' KCONFIG_WERROR - Turn some Kconfig warnings into error conditions'
> > > > > + @echo ' KCONFIG_WARN_UNKNOWN_SYMBOLS - Make Kconfig warn about all unrecognized config symbols'
> > > > >
> > > > > # ===========================================================================
> > > > > # object files used by all kconfig flavours
> > > > > --
> > > > > 2.44.0.rc0.258.g7320e95886-goog
> > > > >
> > > > >
> > > >
> > > > Why only two, while Kconfig supports more env variables?
> > >
> > > Right. I wanted to add only those that we use (and familiar with) for
> > > starters. I'm not familiar with things like KCONFIG_PROBABILITY, for
> > > instance, and not sure how to document it (its Documentation/kbuild/kconfig.rst
> > > description is pretty lengthy).
> >
> > Masahiro, any opinion?
>
>
> I do not need this patch.
Do you agree that putting kconfig env knobs into help makes sense
in general? Especially those add valuable sanity checks.
Powered by blists - more mailing lists