From: "Benno Lossin" <lossin@kernel.org>
To: "Benno Lossin" <benno.lossin@proton.me>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"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>
Cc: <rust-for-linux@vger.kernel.org>
Subject: Re: [PATCH 0/8] pin-init sync for v6.16
Date: Thu, 01 May 2025 18:38:35 +0200 [thread overview]
Message-ID: <D9KZ00WU5YM5.235RJ2R0YSDC9@kernel.org> (raw)
In-Reply-To: <20250421221728.528089-1-benno.lossin@proton.me>
On Tue Apr 22, 2025 at 12:17 AM CEST, Benno Lossin wrote:
> Synchronize changes from the upstream repository for v6.16. Branch with
> all commits on top can be found at [1].
>
> I did not expect that I would synchronize a lot of changes this soon,
> but here we are. They are pretty conservative, so I don't expect anyone
> to object (if you do find something, of course speak up!). A short
> overview of the changes:
>
> * Make the `Zeroable` derive macro compatible with field visibility and
> add union support.
> * Add a new derive macro for `Zeroable` in order to allow deriving it in
> bindgen-generated crates.
> * Add the `Wrapper` trait to allow initializing wrapper types (such as
> `UnsafeCell` and `UnsafePinned`) via pin-initializers.
>
> [1]: https://github.com/y86-dev/linux pin-init/sync
>
> ---
> Cheers,
> Benno
>
> Benno Lossin (4):
> rust: pin-init: add `cast_[pin_]init` functions to change the
> initialized type
> rust: pin-init: allow `pub` fields in `derive(Zeroable)`
> rust: pin-init: allow `Zeroable` derive macro to also be applied to
> unions
> rust: pin-init: add `MaybeZeroable` derive macro
>
> Christian Schrefl (4):
> rust: pin-init: Add the `Wrapper` trait.
> rust: pin-init: Implement `Wrapper` for `UnsafePinned` behind feature
> flag.
> rust: pin-init: Update Changelog and Readme
> rust: pin-init: Update the structural pinning link in readme.
>
> rust/pin-init/README.md | 8 +-
> rust/pin-init/internal/src/lib.rs | 5 +
> rust/pin-init/internal/src/zeroable.rs | 27 +++++-
> rust/pin-init/src/lib.rs | 126 ++++++++++++++++++++++++-
> rust/pin-init/src/macros.rs | 91 +++++++++++++++++-
> 5 files changed, 253 insertions(+), 4 deletions(-)
>
>
> base-commit: 39051adb070432b283e6c11b2b24937281b9f97f
Applied to pin-init-next -- thanks everyone!
---
Cheers,
Benno
prev parent reply other threads:[~2025-05-01 16:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 22:17 [PATCH 0/8] pin-init sync for v6.16 Benno Lossin
2025-04-21 22:17 ` [PATCH 1/8] rust: pin-init: add `cast_[pin_]init` functions to change the initialized type Benno Lossin
2025-04-22 6:56 ` Christian Schrefl
2025-04-21 22:17 ` [PATCH 2/8] rust: pin-init: Add the `Wrapper` trait Benno Lossin
2025-04-22 4:44 ` Boqun Feng
2025-04-21 22:18 ` [PATCH 3/8] rust: pin-init: Implement `Wrapper` for `UnsafePinned` behind feature flag Benno Lossin
2025-04-22 9:42 ` Christian Schrefl
2025-04-22 11:21 ` Benno Lossin
2025-04-22 14:17 ` Christian Schrefl
2025-04-21 22:18 ` [PATCH 4/8] rust: pin-init: Update Changelog and Readme Benno Lossin
2025-04-21 22:18 ` [PATCH 5/8] rust: pin-init: Update the structural pinning link in readme Benno Lossin
2025-04-21 22:18 ` [PATCH 6/8] rust: pin-init: allow `pub` fields in `derive(Zeroable)` Benno Lossin
2025-04-22 4:55 ` Boqun Feng
2025-04-22 8:30 ` Benno Lossin
2025-04-22 14:14 ` Boqun Feng
2025-04-22 14:45 ` Benno Lossin
2025-04-22 21:11 ` Boqun Feng
2025-04-22 21:56 ` Benno Lossin
2025-04-21 22:18 ` [PATCH 7/8] rust: pin-init: allow `Zeroable` derive macro to also be applied to unions Benno Lossin
2025-04-21 22:18 ` [PATCH 8/8] rust: pin-init: add `MaybeZeroable` derive macro Benno Lossin
2025-04-22 4:54 ` Boqun Feng
2025-04-22 7:56 ` Benno Lossin
2025-05-01 16:38 ` 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=D9KZ00WU5YM5.235RJ2R0YSDC9@kernel.org \
--to=lossin@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--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.