From: Julian Braha <julianbraha@gmail.com>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas.schier@linux.dev>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] kconfig: add optional warnings for changed input values
Date: Sat, 13 Jun 2026 13:48:40 +0100 [thread overview]
Message-ID: <7206bc69-c35d-4ce7-8083-ae6586e7543f@gmail.com> (raw)
In-Reply-To: <20260611060000.23858-1-pengpeng@iscas.ac.cn>
On 6/11/26 07:00, Pengpeng Hou wrote:
> When reading .config input, Kconfig stores user-provided values first
> and then resolves the final value after applying dependencies, ranges,
> and other constraints.
>
> If the final value differs from the user input, Kconfig already tracks
> that state internally, but it does not provide a focused diagnostic to
> show which explicit inputs were adjusted. This is particularly confusing
> for requested values that get forced down by unmet dependencies or
> clamped by ranges.
Hi Pengpeng,
This change would be a huge QoL improvement for me, thank you. When I
generate config files with external tooling, I need to do this check
manually.
It would also be helpful if config options that are removed from .config
would be printed, since there are config options that are only defined
in certain architectures.
Tested-by: Julian Braha <julianbraha@gmail.com>
prev parent reply other threads:[~2026-06-13 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 6:00 [PATCH v3] kconfig: add optional warnings for changed input values Pengpeng Hou
2026-06-13 12:48 ` Julian Braha [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=7206bc69-c35d-4ce7-8083-ae6586e7543f@gmail.com \
--to=julianbraha@gmail.com \
--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=nicolas.schier@linux.dev \
--cc=pengpeng@iscas.ac.cn \
/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