From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Nicolas Schier <n.schier@avm.de>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
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: Fri, 1 Mar 2024 23:28:44 +0900 [thread overview]
Message-ID: <20240301142844.GP11972@google.com> (raw)
In-Reply-To: <ZeG2PRYmdO0r44kS@buildd.core.avm.de>
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)
next prev parent reply other threads:[~2024-03-01 14:28 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 [this message]
2024-03-04 6:41 ` Nicolas Schier
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=20240301142844.GP11972@google.com \
--to=senozhatsky@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=n.schier@avm.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.