From: Nicolas Schier <n.schier@avm.de>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] kconfig: add some Kconfig env variables to make help
Date: Mon, 4 Mar 2024 07:41:39 +0100 [thread overview]
Message-ID: <ZeVtIwua9T5prwUl@buildd.core.avm.de> (raw)
In-Reply-To: <20240301142844.GP11972@google.com>
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
next prev parent reply other threads:[~2024-03-04 6:47 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 [this message]
2024-03-05 16:46 ` Masahiro Yamada
2024-03-09 20:24 ` Nicolas Schier
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=ZeVtIwua9T5prwUl@buildd.core.avm.de \
--to=n.schier@avm.de \
--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