From: "Rob Herring (Arm)" <robh@kernel.org>
To: Chaoyi Chen <kernel@airkyi.com>
Cc: devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Heiko Stuebner <heiko@sntech.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Jonas Karlman <jonas@kwiboo.se>,
Quentin Schulz <quentin.schulz@cherry.de>,
linux-kernel@vger.kernel.org,
Kever Yang <kever.yang@rock-chips.com>,
Andrew Lunn <andrew@lunn.ch>,
linux-rockchip@lists.infradead.org,
FUKAUMI Naoki <naoki@radxa.com>,
Jimmy Hon <honyuenkwun@gmail.com>,
Alexey Charkov <alchark@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Chaoyi Chen <chaoyi.chen@rock-chips.com>,
Dragan Simic <dsimic@manjaro.org>,
linux-arm-kernel@lists.infradead.org,
Jianfeng Liu <liujianfeng1994@gmail.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: rockchip: Add rk3399 industry evaluation board
Date: Wed, 30 Apr 2025 09:36:11 -0500 [thread overview]
Message-ID: <174602375195.3396795.11425847299435773154.robh@kernel.org> (raw)
In-Reply-To: <20250430074848.539-2-kernel@airkyi.com>
On Wed, 30 Apr 2025 15:48:47 +0800, Chaoyi Chen wrote:
> From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
>
> Add devicetree binding for the rk3399 industry evaluation board.
>
> Signed-off-by: Chaoyi Chen <chaoyi.chen@rock-chips.com>
> ---
>
> (no changes since v1)
>
> Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
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>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-04-30 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 7:48 [PATCH v2 0/2] Add support for rk3399 industry evaluation board Chaoyi Chen
2025-04-30 7:48 ` [PATCH v2 1/2] dt-bindings: arm: rockchip: Add " Chaoyi Chen
2025-04-30 14:36 ` Rob Herring (Arm) [this message]
2025-04-30 14:48 ` Quentin Schulz
2025-05-02 1:30 ` Rob Herring
2025-04-30 7:48 ` [PATCH v2 2/2] arm64: dts: rockchip: Add rk3399-evb-ind board Chaoyi Chen
2025-04-30 8:39 ` Quentin Schulz
2025-04-30 10:19 ` Chaoyi Chen
2025-04-30 20:56 ` [PATCH v2 0/2] Add support for rk3399 industry evaluation board Rob Herring (Arm)
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=174602375195.3396795.11425847299435773154.robh@kernel.org \
--to=robh@kernel.org \
--cc=alchark@gmail.com \
--cc=andrew@lunn.ch \
--cc=chaoyi.chen@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=geert+renesas@glider.be \
--cc=heiko@sntech.de \
--cc=honyuenkwun@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@airkyi.com \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=liujianfeng1994@gmail.com \
--cc=naoki@radxa.com \
--cc=quentin.schulz@cherry.de \
--cc=sebastian.reichel@collabora.com \
/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