All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Benno Lossin" <lossin@kernel.org>
To: "Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"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>
Subject: Re: [PATCH 0/5] pin-init upstream sync for v7.0
Date: Thu, 19 Mar 2026 10:42:43 +0100	[thread overview]
Message-ID: <DH6NT15UYD86.3UIUPXB6LB91Z@kernel.org> (raw)
In-Reply-To: <20260319093542.3756606-1-lossin@kernel.org>

On Thu Mar 19, 2026 at 10:35 AM CET, Benno Lossin wrote:
> This cycle we have no big changes in pin-init. This series is a
> collection of smaller improvements already merged upstream:
>
> - https://github.com/Rust-for-Linux/pin-init/pull/105
> - https://github.com/Rust-for-Linux/pin-init/pull/110
> - https://github.com/Rust-for-Linux/pin-init/pull/101
> - https://github.com/Rust-for-Linux/pin-init/pull/102
> - https://github.com/Rust-for-Linux/pin-init/pull/108
>
> Next cycle might contain bigger changes, mainly support for tuple
> structs. And I'm also thinking of already starting with integrating
> zerocopy.
>
> While testing for the kernel, I noticed the following issue (already
> fixed in the patch in this series):
>
> - https://github.com/Rust-for-Linux/pin-init/pull/123
>
> This cycle we also had some unsoundness fixes that are already in rc4:
>
> - https://github.com/Rust-for-Linux/pin-init/pull/111
> - https://github.com/Rust-for-Linux/pin-init/pull/117
>
> Lastly, there were some upstream-only changes:
>
> - https://github.com/Rust-for-Linux/pin-init/pull/114
> - https://github.com/Rust-for-Linux/pin-init/pull/109
>
> Cheers,
> Benno
>
>
> Antonio Hickey (1):
>   rust: pin-init: replace `addr_of_mut!` with `&raw mut`
>
> Benno Lossin (1):
>   rust: pin-init: properly document let binding workaround
>
> Gary Guo (2):
>   rust: pin-init: build: simplify use of nightly features
>   rust: pin-init: doc: de-clutter documentation with fake-variadics
>
> Hamdan-Khan (1):
>   rust: pin-init: implement ZeroableOption for NonZero* integer types
>
>  rust/Makefile                                 |  4 +-
>  rust/pin-init/README.md                       |  3 +-
>  rust/pin-init/examples/big_struct_in_place.rs |  3 +
>  rust/pin-init/examples/linked_list.rs         |  3 +-
>  rust/pin-init/examples/mutex.rs               |  3 +-
>  rust/pin-init/examples/pthread_mutex.rs       |  3 +-
>  rust/pin-init/examples/static_init.rs         |  3 +-
>  rust/pin-init/internal/src/init.rs            | 14 +++-
>  rust/pin-init/internal/src/lib.rs             |  2 +-
>  rust/pin-init/src/lib.rs                      | 73 +++++++++++++------
>  10 files changed, 75 insertions(+), 36 deletions(-)
>
>
> base-commit: f338e77383789c0cae23ca3d48adcc5e9e137e3c

The title is of course wrong, it's supposed to be v7.1.

Cheers,
Benno

  parent reply	other threads:[~2026-03-19  9:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19  9:35 [PATCH 0/5] pin-init upstream sync for v7.0 Benno Lossin
2026-03-19  9:35 ` [PATCH 1/5] rust: pin-init: build: simplify use of nightly features Benno Lossin
2026-03-19  9:35 ` [PATCH 2/5] rust: pin-init: properly document let binding workaround Benno Lossin
2026-03-19 11:04   ` Gary Guo
2026-03-19 14:44     ` Benno Lossin
2026-03-19 15:18       ` Gary Guo
2026-03-19  9:35 ` [PATCH 3/5] rust: pin-init: doc: de-clutter documentation with fake-variadics Benno Lossin
2026-03-19  9:35 ` [PATCH 4/5] rust: pin-init: implement ZeroableOption for NonZero* integer types Benno Lossin
2026-03-19  9:35 ` [PATCH 5/5] rust: pin-init: replace `addr_of_mut!` with `&raw mut` Benno Lossin
2026-03-19 11:07   ` Gary Guo
2026-03-19 14:46     ` Benno Lossin
2026-03-19  9:42 ` Benno Lossin [this message]
2026-03-26  8:23 ` [PATCH 0/5] pin-init upstream sync for v7.0 Benno Lossin

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=DH6NT15UYD86.3UIUPXB6LB91Z@kernel.org \
    --to=lossin@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.