From: "Gary Guo" <gary@garyguo.net>
To: "Gary Guo" <gary@garyguo.net>, "Benno Lossin" <lossin@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>,
"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>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>
Cc: <rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rust: pin-init: internal: suppress `explicit_outlives_requirements`
Date: Mon, 12 Oct 2026 00:30:49 +0100 [thread overview]
Message-ID: <DM2EFAJY3CIX.24PPSQQZE0TEW@garyguo.net> (raw)
In-Reply-To: <20261011133904.600785-1-gary@kernel.org>
On Sun Oct 11, 2026 at 2:39 PM BST, Gary Guo wrote:
> From: Gary Guo <gary@garyguo.net>
>
> `#[pin_data]` inserts outlive bounds between lifetimes to allow closure
> callbacks to rely on their relationship. In some cases, these relations are
> implied by fields, and Rust generates `explicit_outlives_requirements`
> allow-by-default lint, which is turned out by kernel as part of
> rust-2018-idioms lint group.
>
> As `#[pin_data]` is a proc macro and it cannot know if the bounds are
> already implied, suppress such lints for generated code.
>
> Signed-off-by: Gary Guo <gary@garyguo.net>
Applied to pin-init-next early, so it gets picked up by Monday's linux-next.
Tags are still welcome.
Best,
Gary
> ---
> rust/pin-init/internal/src/pin_data.rs | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
prev parent reply other threads:[~2026-10-11 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 13:39 [PATCH] rust: pin-init: internal: suppress `explicit_outlives_requirements` Gary Guo
2026-10-11 23:30 ` Gary Guo [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=DM2EFAJY3CIX.24PPSQQZE0TEW@garyguo.net \
--to=gary@garyguo.net \
--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=linux-kernel@vger.kernel.org \
--cc=lossin@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 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.