From: "Gary Guo" <gary@garyguo.net>
To: <gregkh@linuxfoundation.org>, <gary@garyguo.net>, <ojeda@kernel.org>
Cc: <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] rust: pin-init: fix incorrect accessor reference lifetime" failed to apply to 6.6-stable tree
Date: Tue, 12 May 2026 14:19:58 +0100 [thread overview]
Message-ID: <DIGQ8S873GS4.2K07DXYH5QG4W@garyguo.net> (raw)
In-Reply-To: <2026051229-unarmored-shriek-4dc5@gregkh>
On Tue May 12, 2026 at 1:44 PM BST, gregkh wrote:
>
> The patch below does not apply to the 6.6-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
>
> To reproduce the conflict and resubmit, you may use the following commands:
>
> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.6.y
> git checkout FETCH_HEAD
> git cherry-pick -x 68bf102226cf2199dc609b67c1e847cad4de4b57
> # <resolve conflicts, build, test, etc.>
> git commit -s
> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2026051229-unarmored-shriek-4dc5@gregkh' --subject-prefix 'PATCH 6.6.y' HEAD^..
>
> Possible dependencies:
Looks like
https://lore.kernel.org/rust-for-linux/20260325125944.947263-1-lossin@kernel.org/
was reverted in 6.6, so there's nothing to backport here.
The macro is still unsound when packed fields are involved in 6.6, but there's
no in-tree user affected for this version.
So I think it's fine to skip.
Best,
Gary
prev parent reply other threads:[~2026-05-12 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 12:44 FAILED: patch "[PATCH] rust: pin-init: fix incorrect accessor reference lifetime" failed to apply to 6.6-stable tree gregkh
2026-05-12 13:19 ` 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=DIGQ8S873GS4.2K07DXYH5QG4W@garyguo.net \
--to=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=ojeda@kernel.org \
--cc=stable@vger.kernel.org \
/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