From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Miguel Ojeda <ojeda@kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y] rust: Disallow BTF generation with Rust + LTO
Date: Mon, 17 Mar 2025 08:24:09 -0400 [thread overview]
Message-ID: <20250316143924-a1d97475965fdcfe@stable.kernel.org> (raw)
In-Reply-To: <20250316153825.2402903-1-ojeda@kernel.org>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 5daa0c35a1f0e7a6c3b8ba9cb721e7d1ace6e619
WARNING: Author mismatch between patch and upstream commit:
Backport author: Miguel Ojeda<ojeda@kernel.org>
Commit author: Matthew Maurer<mmaurer@google.com>
Status in newer kernel trees:
6.13.y | Present (different SHA1: d0ae348de14f)
6.12.y | Present (different SHA1: 9565f4e43f2f)
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: 5daa0c35a1f0e < -: ------------- rust: Disallow BTF generation with Rust + LTO
-: ------------- > 1: 389af4a62159c rust: Disallow BTF generation with Rust + LTO
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
prev parent reply other threads:[~2025-03-17 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-16 7:16 FAILED: patch "[PATCH] rust: Disallow BTF generation with Rust + LTO" failed to apply to 6.1-stable tree gregkh
2025-03-16 15:38 ` [PATCH 6.1.y] rust: Disallow BTF generation with Rust + LTO Miguel Ojeda
2025-03-17 12:24 ` Sasha Levin [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=20250316143924-a1d97475965fdcfe@stable.kernel.org \
--to=sashal@kernel.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 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.