From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Ying Sun <sunying@nj.iscas.ac.cn>,
Jesse T <mr.bossman075@gmail.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nicolas Schier <nicolas@fjasle.eu>,
Jonathan Corbet <corbet@lwn.net>,
Tomasz Figa <tfiga@chromium.org>,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] kconfig: introduce listunknownconfig
Date: Tue, 22 Aug 2023 15:12:03 +0900 [thread overview]
Message-ID: <20230822061203.GA610023@google.com> (raw)
In-Reply-To: <CAK7LNARTZXvWD8PrA3bC+Ok7LK85qO=pkMs4kOPGn90OBooL6w@mail.gmail.com>
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.
next prev parent reply other threads:[~2023-08-22 6:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 1:19 [RFC][PATCH] kconfig: introduce listunknownconfig Sergey Senozhatsky
2023-08-17 3:44 ` Sergey Senozhatsky
2023-08-19 23:19 ` Masahiro Yamada
2023-08-20 2:45 ` Sergey Senozhatsky
2023-08-20 4:58 ` Sergey Senozhatsky
2023-08-20 5:11 ` Masahiro Yamada
2023-08-20 7:21 ` Sergey Senozhatsky
2023-08-20 7:33 ` Sergey Senozhatsky
2023-08-21 12:27 ` Masahiro Yamada
2023-08-21 16:08 ` Sergey Senozhatsky
2023-08-22 6:12 ` Sergey Senozhatsky [this message]
2023-08-24 1:00 ` Masahiro Yamada
2023-08-24 1:20 ` Sergey Senozhatsky
2023-08-26 1:12 ` Masahiro Yamada
2023-08-26 5:38 ` Masahiro Yamada
2023-08-26 5:53 ` Sergey Senozhatsky
2023-08-24 1:51 ` Tomasz Figa
2023-08-26 1:10 ` Masahiro Yamada
2023-08-26 2:10 ` Sergey Senozhatsky
2023-08-30 7:30 ` Tomasz Figa
2023-08-31 15:28 ` Masahiro Yamada
2023-09-04 5:10 ` Tomasz Figa
2023-12-28 5:51 ` Tomasz Figa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230822061203.GA610023@google.com \
--to=senozhatsky@chromium.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mr.bossman075@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=sunying@nj.iscas.ac.cn \
--cc=tfiga@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).