[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877c0imt1t.fsf@kernel.org>
Date: Tue, 08 Jul 2025 20:33:18 +0200
From: Andreas Hindborg <a.hindborg@...nel.org>
To: Benno Lossin <lossin@...nel.org>
Cc: 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>, Alice Ryhl <aliceryhl@...gle.com>,
Trevor Gross <tmgross@...ch.edu>, Danilo Krummrich <dakr@...nel.org>,
Breno Leitao <leitao@...ian.org>, Fiona Behrens <me@...enk.dev>,
Christian Schrefl <chrisi.schrefl@...il.com>, Alban Kurti
<kurti@...icto.ai>, Michael Vetter <jubalh@...oru.org>,
linux-block@...r.kernel.org, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Rust pin-init for v6.17
Benno Lossin <lossin@...nel.org> writes:
> Hi Miguel,
>
> This time there are a couple of interesting changes, see below. Most
> importantly, we can now use `Result` as an initializer. And implement
> `Zeroable` via the `MaybeZeroable` derive macro. When the second part of
> [1] is merged, this will make all types in bindings that can be zeroed
> implement `Zeroable`.
>
> There is one small mistake in the second commit e832374ccadf ("rust:
> pin-init: change blanket impls for `[Pin]Init` and add one for
> `Result<T, E>`") I forgot to ping Andreas about the changes in Rust
> block and thus don't have his Acked-by. We discussed this privately
> and he his okay with the changes. I didn't rebase due to the fact that
> the commit already is pretty old and that Danilo already merged that
> commit into driver-core-next, see below. Sorry about this!
Acked-by: Andreas Hindborg <a.hindborg@...nel.org>
Best regards,
Andreas Hindborg
Powered by blists - more mailing lists