From: Randy Dunlap <rdunlap@infradead.org>
To: Simon Glass <sjg@chromium.org>, LKML <linux-kernel@vger.kernel.org>
Cc: U-Boot Custodians <u-boot-custodians@lists.denx.de>,
Tom Rini <trini@konsulko.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
barebox@lists.infradead.org,
Sascha Hauer <s.hauer@pengutronix.de>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Jonathan Corbet <corbet@lwn.net>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nicolas Schier <nicolas@fjasle.eu>,
linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [RESEND PATCH] kconfig: Proposed language extension for multiple builds
Date: Fri, 10 Mar 2023 21:39:15 -0800 [thread overview]
Message-ID: <bae2702e-3570-f461-b86f-e56ce82a636e@infradead.org> (raw)
In-Reply-To: <20230310183717.RESEND.1.Idaaf79c3e768b85750d5a7eb732052576c5e07e5@changeid>
Hi--
On 3/10/23 18:37, Simon Glass wrote:
> (I am sending this again to get more feedback)
>
> In the case of Linux, only one build is produced so there is only a
> single configuration. For other projects, such as U-Boot and Zephyr, the
> same code is used to produce multiple builds, each with related (but
> different) options enabled.
>
> This can be handled with the existing kconfig language, but it is quite
> verbose, somewhat tedious and very error-prone, since there is a lot of
> duplication. The result is hard to maintain.
>
> Describe an extension to the Kconfig language to support easier handling
> of this use case.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
IMO Masahiro has already answered this multiple times and I agree with his answers.
For others, the full previous thread is at
https://lore.kernel.org/all/20230219145453.1.Idaaf79c3e768b85750d5a7eb732052576c5e07e5@changeid/
> ---
>
> Documentation/kbuild/kconfig-language.rst | 134 ++++++++++++++++++++++
> 1 file changed, 134 insertions(+)
--
~Randy
next prev parent reply other threads:[~2023-03-11 5:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 2:37 [RESEND PATCH] kconfig: Proposed language extension for multiple builds Simon Glass
2023-03-11 5:39 ` Randy Dunlap [this message]
2023-03-11 16:55 ` Tom Rini
2023-03-12 4:08 ` Boris Kolpackov
2023-03-12 11:05 ` Masahiro Yamada
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=bae2702e-3570-f461-b86f-e56ce82a636e@infradead.org \
--to=rdunlap@infradead.org \
--cc=barebox@lists.infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=s.hauer@pengutronix.de \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot-custodians@lists.denx.de \
--cc=u-boot@lists.denx.de \
--cc=yamada.masahiro@socionext.com \
/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;
as well as URLs for NNTP newsgroup(s).