From: Greg KH <gregkh@linuxfoundation.org>
To: Julian Braha <julianbraha@gmail.com>
Cc: akpm@linux-foundation.org, ljs@kernel.org, arnd@arndb.de,
masahiroy@kernel.org, nathan@kernel.org, nsc@kernel.org,
ojeda@kernel.org, corbet@lwn.net, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] scripts: add kconfirm
Date: Mon, 27 Apr 2026 14:48:19 -0600 [thread overview]
Message-ID: <2026042727-delicate-genre-21fa@gregkh> (raw)
In-Reply-To: <20260427174429.779474-2-julianbraha@gmail.com>
On Mon, Apr 27, 2026 at 06:44:28PM +0100, Julian Braha wrote:
> Add kconfirm into scripts/ and modify the root Makefile and
> scripts/Makefile accordingly so that it can be compiled and run with:
> `make kconfirm`
> from the root of the tree.
You don't say what this fancy new tool actually does anywhere that I can
see :(
>
> The user is expected to have Rust with Cargo installed, and an internet
> connection on the first run to download and compile the dependencies.
>
> Signed-off-by: Julian Braha <julianbraha@gmail.com>
> ---
> Makefile | 12 +-
> scripts/Makefile | 2 +-
> scripts/kconfirm/Cargo.lock | 1710 +++++++++++++++++
Did you mean to check this file in? That's not going to work well...
thanks,
greg k-h
next prev parent reply other threads:[~2026-04-27 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 17:44 [RFC PATCH 0/2] scripts: add kconfirm Julian Braha
2026-04-27 17:44 ` [RFC PATCH 1/2] " Julian Braha
2026-04-27 20:48 ` Greg KH [this message]
2026-04-27 17:44 ` [RFC PATCH 2/2] Documentation: dev-tools: " Julian Braha
2026-04-27 18:17 ` Miguel Ojeda
2026-04-27 19:33 ` Arnd Bergmann
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=2026042727-delicate-genre-21fa@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=julianbraha@gmail.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=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