From: "Benno Lossin" <lossin@kernel.org>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>
Cc: "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>,
"Xiangfei Ding" <dingxiangfei2009@gmail.com>,
stable@kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust: list: fix path of `assert_pinned!`
Date: Mon, 26 May 2025 21:01:06 +0200 [thread overview]
Message-ID: <DA6BORD02WHT.19D9226XGI6GA@kernel.org> (raw)
In-Reply-To: <CANiq72=G5w4D=c4U0KEQnRcy7vmARbWovmJwO3+vkyhixFinjw@mail.gmail.com>
On Mon May 26, 2025 at 8:46 PM CEST, Miguel Ojeda wrote:
> On Sun, May 25, 2025 at 7:34 PM Benno Lossin <lossin@kernel.org> wrote:
>>
>> Commit dbd5058ba60c ("rust: make pin-init its own crate") moved all
>> items from pin-init into the pin-init crate, including the
>> `assert_pinned!` macro.
>>
>> Thus fix the path.
>>
>> This occurrence was missed in that commit, since it has no current
>> users, although binder does.
>>
>> Cc: stable@kernel.org # I haven't found the commit in stable yet, but just to be sure.
>> Fixes: dbd5058ba60c ("rust: make pin-init its own crate")
>> Signed-off-by: Benno Lossin <lossin@kernel.org>
>
> Applied to `rust-next` -- thanks!
>
> [ Reworded slightly as discussed in the list. - Miguel ]
>
> The commit is in v6.15 (rather than just in e.g. rust-next), so it
> should indeed have the Cc: stable (I removed the suffix).
Yes, at the time of writing the commit, I hadn't pulled from Linus'
tree & the stable trees.
Thanks!
---
Cheers,
Benno
prev parent reply other threads:[~2025-05-26 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 17:34 [PATCH] rust: list: fix path of `assert_pinned!` Benno Lossin
2025-05-25 17:39 ` Benno Lossin
2025-05-25 18:51 ` Miguel Ojeda
2025-05-25 18:53 ` Miguel Ojeda
2025-05-25 19:48 ` Benno Lossin
2025-05-26 18:46 ` Miguel Ojeda
2025-05-26 19:01 ` 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=DA6BORD02WHT.19D9226XGI6GA@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=dakr@kernel.org \
--cc=dingxiangfei2009@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=me@kloenk.dev \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).