[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZeVtIwua9T5prwUl@buildd.core.avm.de>
Date: Mon, 4 Mar 2024 07:41:39 +0100
From: Nicolas Schier <n.schier@....de>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: Masahiro Yamada <masahiroy@...nel.org>, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2] kconfig: add some Kconfig env variables to make help
On Fri, Mar 01, 2024 at 11:28:44PM +0900, Sergey Senozhatsky wrote:
> On (24/03/01 12:04), Nicolas Schier wrote:
> > Perhaps it might be a compromise to let 'make help' point to the
> > kbuild/kconfig documentation?
>
> Yes, I was thinking the same. A one-liner description per-env var
> and point to documentation if one-liner is not enough
>
> KCONFIG_BARREL_ROLL - kconfig does a barrel roll
> KCONFIG_FOO_BAR - kconfig does foo and then bar (see
> documentation for details)
No, I thought about leaving out any concrete examples but just adding a
sentence like:
kconfig and kbuild allow tuning and checks by settings various
environment variables, cp. Documentation/kbuild/ for details.
Then there is no need to re-document each variable in 'make help' but
those who are new are explicitly pointed to the maintained
documentation.
Kind regards,
Nicolas
Powered by blists - more mailing lists