[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNAT7+GbXaF6MW18YvEeF4ZZLrn6sOutHPNxcoL_RD1Utyw@mail.gmail.com>
Date: Wed, 6 Mar 2024 01:46:35 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Sergey Senozhatsky <senozhatsky@...omium.org>, 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 Mon, Mar 4, 2024 at 3:41 PM Nicolas Schier <n.schier@....de> wrote:
>
> 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.
That can be a compromised way, but it sounds silly...
Is it helpful at least for people who know 'make help'
but do not know Documentation/kbuild/?
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists