From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Matthew Maurer <mmaurer@google.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
"Alexandre Courbot" <acourbot@nvidia.com>
Subject: Re: [PATCH v5] rust: Add support for feeding entropy to randomness pool
Date: Fri, 23 Jan 2026 00:26:48 +0100 [thread overview]
Message-ID: <aXKyOGeU_z4v8Ep4@zx2c4.com> (raw)
In-Reply-To: <20260102-add-entropy-v5-1-6b38a7a4a9ee@google.com>
On Fri, Jan 02, 2026 at 06:50:16PM +0000, Matthew Maurer wrote:
> Adds just enough support to allow device drivers to feed entropy to the
> central pool.
>
> Reviewed-by: Alice Ryhl <aliceryhl@google.com>
> Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
> Signed-off-by: Matthew Maurer <mmaurer@google.com>
> ---
> This adds bindings for `add_device_randomness` to enable the conversion
> of `qcom-socinfo` to Rust [1].
>
> I'm trying to land it separately because it's much simpler and likely
> usable by others. The conversation around this code is also likely to be
> very different than the conversation about the socinfo driver.
Okay, I can take this. But I just wanted to confirm: is that RFC patch
definitely happening? Should I wait until there's a v1 or something?
Jason
next prev parent reply other threads:[~2026-01-22 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 18:50 [PATCH v5] rust: Add support for feeding entropy to randomness pool Matthew Maurer
2026-01-22 23:26 ` Jason A. Donenfeld [this message]
2026-01-23 17:41 ` Matthew Maurer
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=aXKyOGeU_z4v8Ep4@zx2c4.com \
--to=jason@zx2c4.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mmaurer@google.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=tytso@mit.edu \
/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.