[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK7LNAQ+zTVNjYQ=BFm1s7R9i6W=mz1Sy3wamvaHwNxPzuWOfw@mail.gmail.com>
Date: Sun, 19 Nov 2023 19:02:05 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/6] kconfig: require an exact match for "is not set" to
disable CONFIG option
On Sun, Nov 19, 2023 at 1:30 AM Randy Dunlap <rdunlap@...radead.org> wrote:
>
> 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?
Yes. =n is still supported.
The code diff is
strncmp() -> strcmp().
> 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
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists