From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, justin@tidylabs.net
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6.y] arm64: dts: rockchip: fix u2phy1_host status for NanoPi R4S
Date: Tue, 25 Mar 2025 07:33:41 -0400 [thread overview]
Message-ID: <20250324204329-f86301e0975263a6@stable.kernel.org> (raw)
In-Reply-To: <20250324184509.13634-1-justin@tidylabs.net>
[ 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: 38f4aa34a5f737ea8588dac320d884cc2e762c03
Status in newer kernel trees:
6.13.y | Not found
6.12.y | Not found
Note: The patch differs from the upstream commit:
---
1: 38f4aa34a5f73 ! 1: 3cb1d28a1d80f arm64: dts: rockchip: fix u2phy1_host status for NanoPi R4S
@@ Commit message
Reviewed-by: Dragan Simic <dsimic@manjaro.org>
Link: https://lore.kernel.org/r/20250225170420.3898-1-justin@tidylabs.net
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
+ (cherry picked from commit 38f4aa34a5f737ea8588dac320d884cc2e762c03)
- ## arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtsi ##
-@@ arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dtsi: &u2phy0_host {
+ ## arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts ##
+@@ arch/arm64/boot/dts/rockchip/rk3399-nanopi-r4s.dts: &u2phy0_host {
};
&u2phy1_host {
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
prev parent reply other threads:[~2025-03-25 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 15:30 FAILED: patch "[PATCH] arm64: dts: rockchip: fix u2phy1_host status for NanoPi R4S" failed to apply to 6.6-stable tree gregkh
2025-03-24 18:45 ` [PATCH 6.6.y] arm64: dts: rockchip: fix u2phy1_host status for NanoPi R4S Justin Klaassen
2025-03-25 11:33 ` 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=20250324204329-f86301e0975263a6@stable.kernel.org \
--to=sashal@kernel.org \
--cc=justin@tidylabs.net \
--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