[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230822061203.GA610023@google.com>
Date: Tue, 22 Aug 2023 15:12:03 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Ying Sun <sunying@...iscas.ac.cn>,
Jesse T <mr.bossman075@...il.com>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Nicolas Schier <nicolas@...sle.eu>,
Jonathan Corbet <corbet@....net>,
Tomasz Figa <tfiga@...omium.org>, linux-kbuild@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] kconfig: introduce listunknownconfig
On (23/08/21 21:27), Masahiro Yamada wrote:
>
> My (original) hope was to add a single switch, KCONFIG_VERBOSE, to address both:
>
> - A CONFIG option is hidden by unmet dependency (Ying Sun's case)
> - A CONFIG option no longer exists (your case)
> - Anything else we need to be careful
A quick question: is it too late to suggest an alternative name?
Could KCONFIG_SANITY_CHECKS be a little cleaner? Because we basically
run sanity checks on the config.
And one more question: those sanity checks seem very reasonable.
Is there any reason we would not want to keep them ON by default?
And those brave souls, that do not wish for the tool to very that
the .config is sane and nothing will get downgraded/disabled, can
always set KCONFIG_SANITY_CHECKS to 0.
Powered by blists - more mailing lists