From: Nicolas Schier <nsc@kernel.org>
To: omer zalman <omerzalman42@gmail.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kconfig: keep builtin precedence with duplicate fragment entries
Date: Tue, 29 Sep 2026 14:10:16 +0200 [thread overview]
Message-ID: <aruqqBsCXEhO1pTN@levanger> (raw)
In-Reply-To: <CAGLNFZcFDMD7P3rwueV4eRQ4qvDU4ekyzLmYTFq==5fUZxMBmw@mail.gmail.com>
On Mon, Sep 28, 2026 at 07:45:22PM -0400, omer zalman wrote:
> The -y option is meant to preserve a builtin value when a fragment
> requests a module. With duplicate CONFIG_FOO=m lines, only the last
> fragment line is skipped; an earlier one remains after CONFIG_FOO=y.
> Kconfig reads the later assignment and can demote the symbol. Track
> the symbol instead of one line, and skip all of its assignments
> when builtin precedence applies.
>
> Signed-off-by: Omer Zalman <omerzalman42@gmail.com>
>
> The exact git-format-patch file is attached because Gmail's web
> composer removes tabs from inline diffs.
I did not have time for review, yet; just a heads-up: Sending patches
via attachments is incompatible to standard tooling (b4, etc.) and thus
requires more manual work. One way to work-around gmails restrictions
might be the use of b4's web-submission endpoint:
https://b4.docs.kernel.org/en/latest/contributor/send.html#authenticating-with-the-web-submission-endpoint
--
Nicolas
prev parent reply other threads:[~2026-09-29 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 23:45 omer zalman
2026-09-29 12:10 ` 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=aruqqBsCXEhO1pTN@levanger \
--to=nsc@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=omerzalman42@gmail.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
all inboxes | Powered by JetHome®