From: Jani Nikula <jani.nikula@linux.intel.com>
To: Julian Braha <julianbraha@gmail.com>, Kees Cook <kees@kernel.org>
Cc: nathan@kernel.org, nsc@kernel.org, corbet@lwn.net,
skhan@linuxfoundation.org, arnd@arndb.de,
stefan.hengelein@fau.de, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
nico@fluxnic.net, officialnaumansabir@gmail.com,
rdunlap@infradead.org, vegard.nossum@oracle.com, tj@kernel.org
Subject: Re: [PATCH] Documentation: warn users not to use select on choice options in Kconfig
Date: Wed, 29 Jul 2026 18:10:04 +0300 [thread overview]
Message-ID: <f362ddf2e0f3ecf41ed81f03f77577473c3e21bc@intel.com> (raw)
In-Reply-To: <a4d8cb79-a696-4016-8c8a-a56b14992309@gmail.com>
On Thu, 16 Jul 2026, Julian Braha <julianbraha@gmail.com> wrote:
> Hi Kees,
>
> On 7/16/26 05:19, Kees Cook wrote:
>> Yeah, it'd be good to add a checkpatch or even build-time check too.
>
> I'll look into adding a check for this into the kconfig interpreter.
This. I wish there was a kconfig lint option that would whine about all
the things that kconfig-language.rst explicitly tells you *not* to use
select for. (So I could perhaps eventually stop replying to people with
that stuff.)
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-07-29 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 22:01 [PATCH] Documentation: warn users not to use select on choice options in Kconfig Julian Braha
2026-07-16 4:19 ` Kees Cook
2026-07-16 6:04 ` Julian Braha
2026-07-29 15:10 ` Jani Nikula [this message]
2026-07-21 10:59 ` Nicolas Schier
2026-08-02 19:13 ` Nicolas Schier
2026-08-02 19:36 ` Julian Braha
2026-08-03 17:47 ` Nathan Chancellor
2026-08-03 18:26 ` Julian Braha
2026-08-04 11:47 ` Nicolas Schier
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=f362ddf2e0f3ecf41ed81f03f77577473c3e21bc@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=julianbraha@gmail.com \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nico@fluxnic.net \
--cc=nsc@kernel.org \
--cc=officialnaumansabir@gmail.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=stefan.hengelein@fau.de \
--cc=tj@kernel.org \
--cc=vegard.nossum@oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.