From: "Benno Lossin" <lossin@kernel.org>
To: "Benno Lossin" <lossin@kernel.org>,
"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>,
"Fiona Behrens" <me@kloenk.dev>,
"Christian Schrefl" <chrisi.schrefl@gmail.com>
Cc: <rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] rust: pin-init: rename `project` -> `project_this` in doctest
Date: Thu, 11 Sep 2025 23:32:33 +0200 [thread overview]
Message-ID: <DCQAJK47X6N6.34J94D8MPZARW@kernel.org> (raw)
In-Reply-To: <20250905171209.944599-1-lossin@kernel.org>
On Fri Sep 5, 2025 at 7:12 PM CEST, Benno Lossin wrote:
> The next commit makes the `#[pin_data]` attribute generate a `project`
> function that would collide with any existing ones.
>
> Link: https://github.com/Rust-for-Linux/pin-init/pull/75/commits/67fc90312149fd797078578612aac83b459a6ca4
> Signed-off-by: Benno Lossin <lossin@kernel.org>
Applied to pin-init-next, thanks everyone!
[ Removed spurious comment in patch 2 ]
---
Cheers,
Benno
prev parent reply other threads:[~2025-09-11 21:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 17:12 [PATCH 1/2] rust: pin-init: rename `project` -> `project_this` in doctest Benno Lossin
2025-09-05 17:12 ` [PATCH 2/2] rust: pin-init: add pin projections to `#[pin_data]` Benno Lossin
2025-09-10 10:23 ` Alice Ryhl
2025-09-10 10:24 ` Alice Ryhl
2025-09-10 10:38 ` Benno Lossin
2025-09-10 10:38 ` Benno Lossin
2025-09-10 10:54 ` Alice Ryhl
2025-09-10 12:18 ` Benno Lossin
2025-09-10 12:28 ` Alice Ryhl
2025-09-10 12:52 ` Benno Lossin
2025-09-11 3:31 ` Boqun Feng
2025-09-10 22:20 ` Gary Guo
2025-09-11 21:32 ` 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=DCQAJK47X6N6.34J94D8MPZARW@kernel.org \
--to=lossin@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=chrisi.schrefl@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=me@kloenk.dev \
--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.