Rust for Linux List
 help / color / mirror / Atom feed
From: "Gary Guo" <gary@garyguo.net>
To: "Gary Guo" <gary@garyguo.net>, "Benno Lossin" <lossin@kernel.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"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>
Cc: <rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"Martin Kletzander" <mkletzan@redhat.com>,
	"Mirko Adzic" <adzicmirko97@gmail.com>,
	"Xiaobo Liu" <cppcoffee@gmail.com>
Subject: Re: [PATCH 0/8] rust: pin-init upstream sync for v7.2 (round 2)
Date: Fri, 29 May 2026 22:04:16 +0100	[thread overview]
Message-ID: <DIVGRJP17CSE.1Q6E445IXJ1J@garyguo.net> (raw)
In-Reply-To: <20260527-pin-init-sync-v1-0-e20335ed2501@garyguo.net>

On Wed May 27, 2026 at 6:19 PM BST, Gary Guo wrote:
> This is a second round of patch syncs from upstream pin-init repo.
> The following patches are included.
>
> - Allow other attributes in #[pin_data] structs
>   https://github.com/Rust-for-Linux/pin-init/pull/122
>
> - init: allow `nonstandard_style` for generated accessor/value
>   https://github.com/Rust-for-Linux/pin-init/pull/127
>
> - docs: fix typos in MaybeZeroable documentation
>   https://github.com/Rust-for-Linux/pin-init/pull/154
>
> - Optimize symbol name length of `InitClosure`
>   https://github.com/Rust-for-Linux/pin-init/pull/153
>
> - unwind safety fixes
>   https://github.com/Rust-for-Linux/pin-init/pull/140
>
> Notably the `nonstandard_style` fix will allow a bunch of `#[allow]`s to be
> removed from Nova's codebase.
>
> Signed-off-by: Gary Guo <gary@garyguo.net>
> ---
> Gary Guo (2):
>       rust: pin-init: move `InitClosure` out from `__internal`
>       rust: pin-init: remove `E` from `InitClosure`
>
> Martin Kletzander (1):
>       rust: pin-init: internal: pin_data: filter non-`#[cfg]` attr in generated code
>
> Mirko Adzic (2):
>       rust: pin-init: internal: suppress `non_snake_case` lint in `#[pin_data]`
>       rust: pin-init: internal: suppress `non_snake_case` lint in `[pin_]init!`
>
> Xiaobo Liu (1):
>       rust: pin-init: docs: fix typos in MaybeZeroable documentation

I've applied the above patches to pin-init-next. The two patches below are not
applied and would need a respin.

> Mirko Adzic (2):
>       rust: pin-init: make `[pin_]init_array_from_fn` unwind safe

This one has an issue reported by a Sashiko.

>       rust: pin-init: make `[pin_]chain` unwind safe

And this one triggers a false positive lint in Clippy 1.85, which appears to be
fixed in 1.96. I didn't bother bisecting.

Best,
Gary

>
>  rust/pin-init/internal/src/init.rs     |   4 +-
>  rust/pin-init/internal/src/pin_data.rs |  64 ++++++----
>  rust/pin-init/src/__internal.rs        |  30 -----
>  rust/pin-init/src/lib.rs               | 217 ++++++++++++++++++++++++---------
>  4 files changed, 200 insertions(+), 115 deletions(-)

      parent reply	other threads:[~2026-05-29 21:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27 17:19 [PATCH 0/8] rust: pin-init upstream sync for v7.2 (round 2) Gary Guo
2026-05-27 17:19 ` [PATCH 1/8] rust: pin-init: internal: pin_data: filter non-`#[cfg]` attr in generated code Gary Guo
2026-05-27 17:19 ` [PATCH 2/8] rust: pin-init: internal: suppress `non_snake_case` lint in `#[pin_data]` Gary Guo
2026-05-27 17:19 ` [PATCH 3/8] rust: pin-init: internal: suppress `non_snake_case` lint in `[pin_]init!` Gary Guo
2026-05-27 17:19 ` [PATCH 4/8] rust: pin-init: docs: fix typos in MaybeZeroable documentation Gary Guo
2026-05-27 17:19 ` [PATCH 5/8] rust: pin-init: move `InitClosure` out from `__internal` Gary Guo
2026-05-27 17:19 ` [PATCH 6/8] rust: pin-init: remove `E` from `InitClosure` Gary Guo
2026-05-27 17:19 ` [PATCH 7/8] rust: pin-init: make `[pin_]init_array_from_fn` unwind safe Gary Guo
2026-05-27 17:19 ` [PATCH 8/8] rust: pin-init: make `[pin_]chain` " Gary Guo
2026-05-29 21:04 ` Gary Guo [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=DIVGRJP17CSE.1Q6E445IXJ1J@garyguo.net \
    --to=gary@garyguo.net \
    --cc=a.hindborg@kernel.org \
    --cc=adzicmirko97@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=cppcoffee@gmail.com \
    --cc=dakr@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=mkletzan@redhat.com \
    --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