From: Rahul Rameshbabu <sergeantsagara@protonmail.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts: merge_config: Add flag to prevent unsetting config option
Date: Mon, 07 Aug 2023 04:13:05 +0000 [thread overview]
Message-ID: <875y5rsd6c.fsf@protonmail.com> (raw)
In-Reply-To: <CAK7LNAR_Egr+G9_HmGfrmFAEQ0Tznmbff0w9cJ=1biV5P4PmNQ@mail.gmail.com>
On Sun, 06 Aug, 2023 23:19:55 +0900 "Masahiro Yamada" <masahiroy@kernel.org> wrote:
> On Sun, Jul 30, 2023 at 6:42 AM Rahul Rameshbabu
> <sergeantsagara@protonmail.com> wrote:
>>
>> Overriding a previously defined entry for a config option with 'is not set'
>> may be undesirable in some fragment configuration setups.
>
> Then, you should remove the 'is not set' entry from the fragment.
I had a feeling that was the expectation. Just for reference, my flow
for generating fragments looks like the following.
1. make allnoconfig
2. make menuconfig # select the options that I desire for the fragment
We can drop this patch if this is the expected developer flow. I
realized that overriding with 'is not set' entries in a fragment is
likely desirable, so I made this behavior change as part of a flag that
can be set by the user.
--
Thanks,
Rahul Rameshbabu
next prev parent reply other threads:[~2023-08-07 4:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 21:41 [PATCH] scripts: merge_config: Add flag to prevent unsetting config option Rahul Rameshbabu
2023-08-06 14:19 ` Masahiro Yamada
2023-08-07 4:13 ` Rahul Rameshbabu [this message]
2023-08-07 19:04 ` Masahiro Yamada
2023-08-12 16:44 ` Rahul Rameshbabu
2023-08-16 3:18 ` 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=875y5rsd6c.fsf@protonmail.com \
--to=sergeantsagara@protonmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.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