From: Nicolas Schier <nsc@kernel.org>
To: Julian Braha <julianbraha@gmail.com>
Cc: Nathan Chancellor <nathan@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, kees@kernel.org,
tj@kernel.org
Subject: Re: [PATCH] Documentation: warn users not to use select on choice options in Kconfig
Date: Tue, 4 Aug 2026 13:47:16 +0200 [thread overview]
Message-ID: <anHRRDliJ777LnhB@levanger> (raw)
In-Reply-To: <58a8c7fe-378e-44be-80d1-01479c425f5a@gmail.com>
On Mon, Aug 03, 2026 at 07:26:28PM +0100, Julian Braha wrote:
> On 8/3/26 18:47, Nathan Chancellor wrote:
> > It looks like number 4 has been picked up as well. Given that we only
> > need three more patches to be accepted to turn this into a hard error, I
> > think it would be better to hold off on taking the documentation patch
> > and just push for the hard error next cycle. If these patches are not
> > applied to other trees before 7.3-rc1, we can ask to take them via
> > Kbuild with Acks and/or stable branches for 7.4.
sounds good. I'll prepare a patch for the hard error.
> All good on my end, we can drop this patch.
thanks, removed commit 63dad1769941 ("Documentation: warn users not to
use select on choice options in Kconfig") from kbuild-next-unstable.
>
> - Julian Braha
--
Nicolas
prev parent reply other threads:[~2026-08-04 11:47 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
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 [this message]
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=anHRRDliJ777LnhB@levanger \
--to=nsc@kernel.org \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox