From: Conor Dooley <conor@kernel.org>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: heiko@sntech.de, linux-rockchip@lists.infradead.org,
Andy Yan <andyshrk@163.com>,
Chris Morgan <macromorgan@hotmail.com>,
Conor Dooley <conor+dt@kernel.org>,
Dragan Simic <dsimic@manjaro.org>,
Jonas Karlman <jonas@kwiboo.se>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Tim Lunn <tim@feathertop.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] dt-bindings: arm: rockchip: Add rk3576 evb1 board
Date: Thu, 5 Dec 2024 17:14:48 +0000 [thread overview]
Message-ID: <20241205-judicial-drainpipe-645f3abe07fd@spud> (raw)
In-Reply-To: <20241205103623.878181-6-kever.yang@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 229 bytes --]
On Thu, Dec 05, 2024 at 06:36:22PM +0800, Kever Yang wrote:
> Add device tree documentation for rk3576-evb1-v10.
>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-12-05 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 10:36 [PATCH 0/6] Rockchip: add Rockchip rk3576 EVB1 board Kever Yang
2024-12-05 10:36 ` [PATCH 1/6] dt-bindings: PCI: dwc: rockchip: Add rk3576 support Kever Yang
2024-12-05 11:30 ` Heiko Stübner
2024-12-05 17:05 ` Conor Dooley
2024-12-05 10:36 ` [PATCH 2/6] dts: arm64: rockchip: Add rk3576 naneng combphy nodes Kever Yang
2024-12-05 10:36 ` [PATCH 3/6] dts: arm64: rockchip: Add rk3576 pcie nodes Kever Yang
2024-12-05 10:36 ` [PATCH 4/6] dt-bindings: arm: rockchip: Sort for rk3568 evb Kever Yang
2024-12-05 17:14 ` Conor Dooley
2024-12-05 10:36 ` [PATCH 5/6] dt-bindings: arm: rockchip: Add rk3576 evb1 board Kever Yang
2024-12-05 17:14 ` Conor Dooley [this message]
2024-12-05 10:36 ` [PATCH 6/6] arm64: dts: " Kever Yang
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=20241205-judicial-drainpipe-645f3abe07fd@spud \
--to=conor@kernel.org \
--cc=andyshrk@163.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--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=macromorgan@hotmail.com \
--cc=robh@kernel.org \
--cc=tim@feathertop.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