From: Julian Braha <julianbraha@gmail.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: nsc@kernel.org, ojeda@kernel.org, akpm@linux-foundation.org,
jani.nikula@linux.intel.com, gary@garyguo.net,
gregkh@linuxfoundation.org, arnd@arndb.de, ljs@kernel.org,
andrew.jones@linux.dev, masahiroy@kernel.org, corbet@lwn.net,
qingfang.deng@linux.dev, demiobenour@gmail.com, ej@inai.de,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v4 0/5] add kconfirm
Date: Sun, 6 Sep 2026 16:22:21 +0100 [thread overview]
Message-ID: <4bdaab67-87d7-4c5c-8cb5-ac0f9add4d97@gmail.com> (raw)
In-Reply-To: <20260904220559.GB2787252@ax162>
On 9/4/26 23:05, Nathan Chancellor wrote:
> My apologies for not getting to this sooner, I have been busy with some
> other projects. I will try to play around with this from a usability
> perspective (which is what I am most concerned with at this point). If a
> v5 is mostly prepared, I would not mind seeing it even if we want to go
> the in-tree interpreter checks. One option is to take kconfirm into the
> tree, fix up the warnings it generates, then moving the checks into the
> interpreter directly while dropping them from kconfirm (since the tree
> should be clean at that point). I am open to opinions on that though.
>
Your strategy makes sense to me. I'll send v5 then, but I'd also like to
make sure that Nicolas is onboard with this idea.
- Julian Braha
next prev parent reply other threads:[~2026-09-06 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 0:16 [PATCH v4 0/5] add kconfirm Julian Braha
2026-07-27 0:16 ` [PATCH v4 1/5] kconfig: add add another callback to the parser to view raw parse tree Julian Braha
2026-07-27 0:16 ` [PATCH 2/5] kconfig: add kconfirm Julian Braha
2026-07-27 0:16 ` [PATCH v4 3/5] kconfirm: add tests Julian Braha
2026-07-27 0:16 ` [PATCH v4 4/5] Documentation: add kconfirm Julian Braha
2026-07-27 0:16 ` [PATCH v4 5/5] MAINTAINERS: add entry for kconfirm Julian Braha
2026-09-04 12:29 ` [PATCH v4 0/5] add kconfirm Julian Braha
2026-09-04 18:37 ` Nicolas Schier
2026-09-04 22:05 ` Nathan Chancellor
2026-09-06 15:22 ` Julian Braha [this message]
2026-09-07 8:34 ` 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=4bdaab67-87d7-4c5c-8cb5-ac0f9add4d97@gmail.com \
--to=julianbraha@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.jones@linux.dev \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=demiobenour@gmail.com \
--cc=ej@inai.de \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--cc=qingfang.deng@linux.dev \
--cc=rust-for-linux@vger.kernel.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