From: "Benno Lossin" <lossin@kernel.org>
To: "Benno Lossin" <lossin@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Fiona Behrens" <me@kloenk.dev>,
"Christian Schrefl" <chrisi.schrefl@gmail.com>
Cc: "Oleksandr Babak" <alexanderbabak@proton.me>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] rust: pin-init: Implement `InPlaceWrite<T>` for `&'static mut MaybeUninit<T>`
Date: Sat, 17 Jan 2026 10:54:25 +0100 [thread overview]
Message-ID: <DFQRURCFSDK1.1AJU43WLGBXK2@kernel.org> (raw)
In-Reply-To: <20260108124318.3142999-1-lossin@kernel.org>
On Thu Jan 8, 2026 at 1:43 PM CET, Benno Lossin wrote:
> From: Oleksandr Babak <alexanderbabak@proton.me>
>
> This feature allows users to use `&'static mut MaybeUninit<T>` as a
> place to initialize the value. It mirrors an existing implemetation
> for `Box<MaybeUninit>`, but enables users to use external allocation
> mechanisms such as `static_cell` [1].
>
> Signed-off-by: Oleksandr Babak <alexanderbabak@proton.me>
> Link: https://crates.io/crates/static_cell [1]
> [ Added link to `static_cell` - Benno ]
> Signed-off-by: Benno Lossin <lossin@kernel.org>
> ---
> This is the entire pin-init update this cycle. (excluding the syn
> patches, which I will send soon)
> ---
> rust/pin-init/src/lib.rs | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
Applied to pin-init-next, thanks everyone!
Cheers,
Benno
prev parent reply other threads:[~2026-01-17 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 12:43 Benno Lossin
2026-01-17 9:54 ` Benno Lossin [this message]
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=DFQRURCFSDK1.1AJU43WLGBXK2@kernel.org \
--to=lossin@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alexanderbabak@proton.me \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=chrisi.schrefl@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=me@kloenk.dev \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®