From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, ojeda@kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.14.y] rust: allow Rust 1.87.0's `clippy::ptr_eq` lint
Date: Mon, 12 May 2025 17:52:03 -0400 [thread overview]
Message-ID: <20250512161203-42665e86cc8a03b7@stable.kernel.org> (raw)
In-Reply-To: <20250512124718.1403201-1-ojeda@kernel.org>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found matching upstream commit but patch is missing proper reference to it
Found matching upstream commit: a39f3087092716f2bd531d6fdc20403c3dc2a879
Note: The patch differs from the upstream commit:
---
1: a39f308709271 ! 1: f5e8bab8b025c rust: allow Rust 1.87.0's `clippy::ptr_eq` lint
@@ Commit message
Link: https://lore.kernel.org/r/20250502140237.1659624-3-ojeda@kernel.org
[ Converted to `allow`s since backport was confirmed. - Miguel ]
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
+ (cherry picked from commit a39f3087092716f2bd531d6fdc20403c3dc2a879)
+ Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
## rust/kernel/alloc/kvec.rs ##
@@
@@ rust/kernel/list.rs
+// May not be needed in Rust 1.87.0 (pending beta backport).
+#![allow(clippy::ptr_eq)]
+
+ use crate::init::PinInit;
use crate::sync::ArcBorrow;
use crate::types::Opaque;
- use core::iter::{DoubleEndedIterator, FusedIterator};
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.14.y | Success | Success |
prev parent reply other threads:[~2025-05-12 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 9:02 FAILED: patch "[PATCH] rust: allow Rust 1.87.0's `clippy::ptr_eq` lint" failed to apply to 6.14-stable tree gregkh
2025-05-12 12:47 ` [PATCH 6.14.y] rust: allow Rust 1.87.0's `clippy::ptr_eq` lint Miguel Ojeda
2025-05-12 21:52 ` 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=20250512161203-42665e86cc8a03b7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox