Re: [PATCH v2] merge_config.sh: do not report some differencess between input and output

From: Lukasz Stelmach
Date: Wed Feb 08 2023 - 08:22:01 EST


It was <2023-02-08 śro 14:07>, when Łukasz Stelmach wrote:
> If an input config file contains CONFIG_FOO=n the output one
> will contain a line '# CONFIG_FOO is not set'. merge_config.sh
> should not report it as difference because the end result of
> CONFIG_FOO being disabled is achieved.
>
> Inexistence of CONFIG_FOO (because of unment dependencies) in case
> CONFIG_FOO=n is requested, should also be ignored.
>
> Change-Id: I129f3a0b4205a76d8c42020f8adb72b1889d75fb

Do you want me to resend without this one?

> Signed-off-by: Łukasz Stelmach <l.stelmach@xxxxxxxxxxx>
> ---
> Changes in v2:
> - suppress reports reports if an option was "not set" in input files
> but is missing from the filnal .config due to unmet dependecies.
> - apply the same logic to suppress some reports during the merging
> phase
>
> BTW. Do you think adding "| sort -u" after "grep -w" to avoid reports
> about repeated entries may make sense or do you want such reports to
> be printed.
>
> scripts/kconfig/merge_config.sh | 30 ++++++++++++++++++++----------
> 1 file changed, 20 insertions(+), 10 deletions(-)

[...]


--
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

Attachment: signature.asc
Description: PGP signature