Re: [PATCH v3] kconfig: add optional warnings for changed input values

[Julian Braha]

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@xxxxxxxxx>