[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72k8kWHeBGLgHVE6vN36n6ashq-TVX3+h6WxLtc1jpUefQ@mail.gmail.com>
Date: Thu, 14 Aug 2025 17:33:46 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Paul Moore <paul@...l-moore.com>
Cc: Benno Lossin <lossin@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>,
Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Andreas Hindborg <a.hindborg@...nel.org>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>, Fiona Behrens <me@...enk.dev>, Jocelyn Falempe <jfalempe@...hat.com>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 07/11] rust: security: replace `core::mem::zeroed` with `pin_init::zeroed`
On Thu, Aug 14, 2025 at 5:31 PM Miguel Ojeda
<miguel.ojeda.sandonis@...il.com> wrote:
>
> I think the idea is to take all these through the Rust one with
Or through the pin-init one, which gets pulled into the Rust one.
Cheers,
Miguel
Powered by blists - more mailing lists