From: Benno Lossin <lossin@kernel.org>
To: gary@garyguo.net
Cc: a.hindborg@kernel.org, acourbot@nvidia.com, aliceryhl@google.com,
bjorn3_gh@protonmail.com, boqun@kernel.org, dakr@kernel.org,
daniel.almeida@collabora.com, linux-kernel@vger.kernel.org,
lossin@kernel.org, ojeda@kernel.org,
rust-for-linux@vger.kernel.org, tamird@kernel.org,
tmgross@umich.edu, work@onurozkan.dev
Subject: Re: [PATCH 0/8] rust: pin-init: various cleanups to prepare for self-reference
Date: Wed, 7 Oct 2026 11:20:45 +0100 [thread overview]
Message-ID: <20261007102045.1593329-1-lossin@kernel.org> (raw)
In-Reply-To: <20261006-dev-selfref-dep-v1-0-da716f740d6d@garyguo.net>
On 06 Oct 2026 17:29:30 +0200, Gary Guo <gary@garyguo.net> wrote:
> Pin-init self reference is going to be a big feature, touching various
> places in pin_data and init macros. Do some various cleanups to tidy up the
> macro codebase, so the feature can land without much refactoring.
>
> Details in commits.
>
> Signed-off-by: Gary Guo <gary@garyguo.net>
> ---
> Gary Guo (8):
> rust: pin-init: internal: init: forget guards in reverse order
> rust: pin-init: internal: init: set span location of guards
> rust: pin-init: internal: add utility to handle generics merging
> rust: pin-init: internal: add utility for extract a single attribute
> rust: pin-init: internal: pin_data: move projection struct into `const _: ()` block
> rust: pin-init: internal: pin_data: extract `#[cfg]` processing to its own function
> rust: pin-init: internal: pin_data: rename `'__pin` lifetime to `'__this`
> rust: pin-init: internal: pin_data: parse into `StructInfo` before generating
>
> rust/pin-init/internal/src/init.rs | 19 +--
> rust/pin-init/internal/src/lib.rs | 3 +-
> rust/pin-init/internal/src/pin_data.rs | 217 +++++++++++++++++++++------------
> rust/pin-init/internal/src/util.rs | 189 +++++++++++++++++++++++++++-
> 4 files changed, 341 insertions(+), 87 deletions(-)
these are good improvements. looking forward to seeing the self-ref here!
Acked-by: Benno Lossin <lossin@kernel.org>
best,
Benno
> ---
> base-commit: 499b8f8a5d0401a6ab83b346a307f923640a024a
> change-id: 20261006-dev-selfref-dep-df01df1d05bf
>
> Best regards,
> --
> Gary Guo <gary@garyguo.net>
prev parent reply other threads:[~2026-10-07 10:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 15:29 Gary Guo
2026-10-06 15:29 ` [PATCH 1/8] rust: pin-init: internal: init: forget guards in reverse order Gary Guo
2026-10-06 15:29 ` [PATCH 2/8] rust: pin-init: internal: init: set span location of guards Gary Guo
2026-10-06 15:29 ` [PATCH 3/8] rust: pin-init: internal: add utility to handle generics merging Gary Guo
2026-10-06 15:29 ` [PATCH 4/8] rust: pin-init: internal: add utility for extract a single attribute Gary Guo
2026-10-06 15:29 ` [PATCH 5/8] rust: pin-init: internal: pin_data: move projection struct into `const _: ()` block Gary Guo
2026-10-06 15:29 ` [PATCH 6/8] rust: pin-init: internal: pin_data: extract `#[cfg]` processing to its own function Gary Guo
2026-10-06 15:29 ` [PATCH 7/8] rust: pin-init: internal: pin_data: rename `'__pin` lifetime to `'__this` Gary Guo
2026-10-06 15:29 ` [PATCH 8/8] rust: pin-init: internal: pin_data: parse into `StructInfo` before generating Gary Guo
2026-10-07 10:20 ` 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=20261007102045.1593329-1-lossin@kernel.org \
--to=lossin@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®