From: Nicolas Schier <nicolas@fjasle.eu>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] kconfig: add some Kconfig env variables to make help
Date: Sat, 9 Mar 2024 21:24:42 +0100 [thread overview]
Message-ID: <ZezFirN5okYdhL1U@fjasle.eu> (raw)
In-Reply-To: <CAK7LNAT7+GbXaF6MW18YvEeF4ZZLrn6sOutHPNxcoL_RD1Utyw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
On Wed, Mar 06, 2024 at 01:46:35AM +0900 Masahiro Yamada wrote:
> On Mon, Mar 4, 2024 at 3:41 PM Nicolas Schier <n.schier@avm.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/?
Touché, that's probably right.
Kind regards,
Nicolas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-03-09 20:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 3:12 [PATCH] kconfig: add some Kconfig env variables to make help Sergey Senozhatsky
2024-02-22 3:18 ` Sergey Senozhatsky
2024-02-22 3:25 ` [PATCHv2] " Sergey Senozhatsky
2024-02-22 4:57 ` Masahiro Yamada
2024-02-22 5:16 ` Sergey Senozhatsky
2024-02-28 4:56 ` Sergey Senozhatsky
2024-02-29 2:03 ` Masahiro Yamada
2024-02-29 2:10 ` Sergey Senozhatsky
2024-02-29 3:36 ` Masahiro Yamada
2024-02-29 3:47 ` Sergey Senozhatsky
2024-02-29 15:35 ` Masahiro Yamada
2024-03-01 4:33 ` Sergey Senozhatsky
2024-03-01 11:04 ` Nicolas Schier
2024-03-01 14:28 ` Sergey Senozhatsky
2024-03-04 6:41 ` Nicolas Schier
2024-03-05 16:46 ` Masahiro Yamada
2024-03-09 20:24 ` Nicolas Schier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZezFirN5okYdhL1U@fjasle.eu \
--to=nicolas@fjasle.eu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=senozhatsky@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox