From: Gary Guo <gary@garyguo.net>
To: Benno Lossin <lossin@kernel.org>, Miguel Ojeda <ojeda@kernel.org>
Cc: "Boqun Feng" <boqun@kernel.org>,
"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>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
"Gary Guo" <gary@garyguo.net>,
"Luiz Georg" <luizgngeorg@gmail.com>,
"Mohamad Alsadhan" <mo@sdhn.cc>,
"Mirko Adzic" <adzicmirko97@gmail.com>
Subject: [PATCH 0/7] rust: pin-init: upstream synchronization for 7.3 (round 1)
Date: Fri, 10 Jul 2026 17:20:30 +0100 [thread overview]
Message-ID: <20260710-pin-init-sync-v1-0-8fa16cde87ae@garyguo.net> (raw)
This is a series that synchronize pin-init upstream.
It includes the following merged PR:
- internal: error on duplicate `#[pin]` attribute
https://github.com/Rust-for-Linux/pin-init/pull/120
It includes the following PR that I intend to merge soon:
- Lint cleanups
https://github.com/Rust-for-Linux/pin-init/pull/160
- unwind safety fixes
https://github.com/Rust-for-Linux/pin-init/pull/140
Signed-off-by: Gary Guo <gary@garyguo.net>
---
Gary Guo (4):
rust: pin-init: examples: fix incorrect drop
rust: pin-init: remove redundant clippy expects in doc tests
rust: pin-init: internal: stop using `expect` in macro expansion
rust: pin-init: internal: generate brace in macro for init code blocks
Luiz Georg (1):
rust: pin-init: internal: error on duplicate `#[pin]` attribute
Mirko Adzic (2):
rust: pin-init: make `[pin_]init_array_from_fn` unwind safe
rust: pin-init: make `[pin_]chain` unwind safe
rust/pin-init/examples/mutex.rs | 5 +-
rust/pin-init/internal/src/init.rs | 8 +-
rust/pin-init/internal/src/pin_data.rs | 10 +--
rust/pin-init/src/lib.rs | 151 ++++++++++++++++++++-------------
4 files changed, 101 insertions(+), 73 deletions(-)
---
base-commit: dc59e4fea9d83f03bad6bddf3fa2e52491777482
change-id: 20260710-pin-init-sync-a4cee08c619c
Best regards,
--
Gary Guo <gary@garyguo.net>
next reply other threads:[~2026-07-10 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 16:20 Gary Guo [this message]
2026-07-10 16:20 ` [PATCH 1/7] rust: pin-init: internal: error on duplicate `#[pin]` attribute Gary Guo
2026-07-10 16:20 ` [PATCH 2/7] rust: pin-init: examples: fix incorrect drop Gary Guo
2026-07-10 16:20 ` [PATCH 3/7] rust: pin-init: remove redundant clippy expects in doc tests Gary Guo
2026-07-10 16:20 ` [PATCH 4/7] rust: pin-init: internal: stop using `expect` in macro expansion Gary Guo
2026-07-10 16:20 ` [PATCH 5/7] rust: pin-init: internal: generate brace in macro for init code blocks Gary Guo
2026-07-10 16:20 ` [PATCH 6/7] rust: pin-init: make `[pin_]init_array_from_fn` unwind safe Gary Guo
2026-07-10 16:20 ` [PATCH 7/7] rust: pin-init: make `[pin_]chain` " Gary Guo
2026-07-13 11:50 ` [PATCH 0/7] rust: pin-init: upstream synchronization for 7.3 (round 1) Gary Guo
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=20260710-pin-init-sync-v1-0-8fa16cde87ae@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=adzicmirko97@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=luizgngeorg@gmail.com \
--cc=mo@sdhn.cc \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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