[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3e879452-bda7-46d9-93fa-0cf01e484798@infradead.org>
Date: Sat, 18 Nov 2023 08:30:02 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Masahiro Yamada <masahiroy@...nel.org>,
linux-kbuild@...r.kernel.org
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/6] kconfig: require an exact match for "is not set" to
disable CONFIG option
Hi,
On 11/17/23 23:59, Masahiro Yamada wrote:
> Currently, any string starting "is not set" disables a CONFIG option.
>
> For example, "# CONFIG_FOO is not settled down" is accepted as valid
> input, functioning the same as "# CONFIG_FOO is not set". It is a
> long-standing oddity.
>
> Check the line against the exact pattern "is not set".
>
Just to confirm (I hope), using:
CONFIG_FOO=n
will also still work to disable that config option?
Thanks.
> Signed-off-by: Masahiro Yamada <masahiroy@...nel.org>
> ---
>
> scripts/kconfig/confdata.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/kconfig/confdata.c b/scripts/kconfig/confdata.c
> index 795ac6c9378f..958be12cd621 100644
> --- a/scripts/kconfig/confdata.c
> +++ b/scripts/kconfig/confdata.c
> @@ -454,7 +454,7 @@ int conf_read_simple(const char *name, int def)
> if (!p)
> continue;
> *p++ = 0;
> - if (strncmp(p, "is not set", 10))
> + if (strcmp(p, "is not set"))
> continue;
>
> val = "n";
--
~Randy
Powered by blists - more mailing lists