public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Jimmy Hon <honyuenkwun@gmail.com>
Cc: Ondrej Jirman <megi@xff.cz>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org,
	Jimmy Hon <honyuenkwun@gmail.com>
Subject: Re: [PATCH v7 1/4] arm64: dts: rockchip: refactor common rk3588-orangepi-5.dtsi
Date: Wed, 08 Jan 2025 23:00:56 +0100	[thread overview]
Message-ID: <2727495.q0ZmV6gNhb@diego> (raw)
In-Reply-To: <20250105222614.2359-2-honyuenkwun@gmail.com>

Hi Jimmy,

Am Sonntag, 5. Januar 2025, 23:26:10 CET schrieb Jimmy Hon:
> Orange Pi now has multiple SBCs using the RK3588.
> 
> Refactor the common parts of the Orange Pi 5 Plus DTS so it can be
> shared with the 5 Max and the 5 Ultra.
> 
> Signed-off-by: Jimmy Hon <honyuenkwun@gmail.com>

I'm sorry for having to ask you that, but I did apply Chen-Yu's
patch enabling usb3 on the orange-pi-5-plus [0] which in turn
causes your series to not apply anymore.

So could you rebase once more?

Thanks a lot
Heiko


[0] https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/commit/?h=v6.14-armsoc/dts64&id=a15d12f36eb78692d5c3ebd8a5db7fddf3ea160c




  reply	other threads:[~2025-01-08 22:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-05 22:26 [PATCH v7 0/4] Orange Pi 5 Max Jimmy Hon
2025-01-05 22:26 ` [PATCH v7 1/4] arm64: dts: rockchip: refactor common rk3588-orangepi-5.dtsi Jimmy Hon
2025-01-08 22:00   ` Heiko Stübner [this message]
2025-01-05 22:26 ` [PATCH v7 2/4] dt-bindings: arm: rockchip: Add Xunlong Orange Pi 5 Max Jimmy Hon
2025-01-05 22:26 ` [PATCH v7 3/4] arm64: dts: rockchip: Add Orange Pi 5 Max board Jimmy Hon
2025-01-05 22:26 ` [PATCH v7 4/4] arm64: dts: rockchip: Enable HDMI1 on Orange Pi 5 Max Jimmy Hon

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=2727495.q0ZmV6gNhb@diego \
    --to=heiko@sntech.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=honyuenkwun@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=megi@xff.cz \
    --cc=robh@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