From: "Gary Guo" <gary@garyguo.net>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"Arnd Bergmann" <arnd@arndb.de>
Cc: "Julian Braha" <julianbraha@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>, <ljs@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nsc@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Jonathan Corbet" <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 2/2] Documentation: dev-tools: add kconfirm
Date: Tue, 28 Apr 2026 13:58:52 +0100 [thread overview]
Message-ID: <DI4T1009OWYM.97DRX8ZRWWP@garyguo.net> (raw)
In-Reply-To: <CANiq72mEgpe-UGMQ_YWb8SKsY96Oc0b4sQ_MKvhMDVkNC9WvQA@mail.gmail.com>
On Tue Apr 28, 2026 at 12:51 PM BST, Miguel Ojeda wrote:
>
> Then I thought if the same would apply to `clap` etc., but then again,
> we may want to write more tools like this in Rust in the future (we
> already felt the pain in the past the pain of not having a e.g. JSON
> parser), and whether we could have a more general solution for this,
> including perhaps even a kernel.org registry (either as primary or
> not) etc.
Personally, I think if Internet access is needed, downloading from whatever
registry doesn't really matter as long as we can guarantee that it doesn't
download random packages. Cryptographic hashes would be sufficient for that.
For the part of "not downloading random packages" but only those that are
audited by kernel community -- it could be achieved by using cargo-vet and we
can maintain a shared list of vetted dependencies.
Best,
Gary
next prev parent reply other threads:[~2026-04-28 12:58 UTC|newest]
Thread overview: 10+ 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
2026-04-28 7:01 ` Jonathan Corbet
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
2026-04-28 11:51 ` Miguel Ojeda
2026-04-28 12:58 ` Gary Guo [this message]
2026-04-28 8:23 ` Jani Nikula
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=DI4T1009OWYM.97DRX8ZRWWP@garyguo.net \
--to=gary@garyguo.net \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--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=miguel.ojeda.sandonis@gmail.com \
--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