From: "Rob Herring (Arm)" <robh@kernel.org>
To: Jimmy Hon <honyuenkwun@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Ondrej Jirman <megi@xff.cz>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3 v3] dt-bindings: arm: rockchip: Add Xunlong Orange Pi 5 Max
Date: Mon, 11 Nov 2024 14:57:46 -0600 [thread overview]
Message-ID: <173135828350.1935626.3279818343954125790.robh@kernel.org> (raw)
In-Reply-To: <20241111045408.1922-5-honyuenkwun@gmail.com>
On Sun, 10 Nov 2024 22:53:25 -0600, Jimmy Hon wrote:
> Add devicetree binding for the Xunlong Orange Pi 5 Max board.
>
> The Orange Pi 5 Max is a single board computer powered by the Rockchip
> RK3588 similar to the Orange Pi 5 Plus.
>
> Signed-off-by: Jimmy Hon <honyuenkwun@gmail.com>
> ---
> Documentation/devicetree/bindings/arm/rockchip.yaml | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.
If a tag was not added on purpose, please state why and what changed.
Missing tags:
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
next prev parent reply other threads:[~2024-11-11 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 4:53 [PATCH 0/3 v3] arm64: dts: rockchip: Add Orange Pi 5 Max board Jimmy Hon
2024-11-11 4:53 ` [PATCH 1/3 v3] arm64: dts: rockchip: refactor common rk3588-orangepi-5.dtsi Jimmy Hon
2024-11-11 4:53 ` [PATCH 2/3 v3] dt-bindings: arm: rockchip: Add Xunlong Orange Pi 5 Max Jimmy Hon
2024-11-11 20:15 ` Conor Dooley
2024-11-11 20:57 ` Rob Herring (Arm) [this message]
2024-11-13 5:15 ` Jimmy Hon
2024-11-11 4:53 ` [PATCH 3/3 v3] arm64: dts: rockchip: Add Orange Pi 5 Max board Jimmy Hon
2024-11-15 16:15 ` Marco Schirrmeister
2024-11-15 16:56 ` Jimmy Hon
2024-12-07 21:44 ` Marco Schirrmeister
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=173135828350.1935626.3279818343954125790.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--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 \
/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