From: Rob Herring <robh@kernel.org>
To: djw@t-chip.com.cn
Cc: "Jagan Teki" <jagan@amarulasolutions.com>,
"Uwe Kleine-König" <uwe@kleine-koenig.org>,
"Liang Chen" <cl@rock-chips.com>,
"Rob Herring" <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
"Wayne Chou" <zxf@t-chip.com.cn>,
linux-kernel@vger.kernel.org, "Heiko Stuebner" <heiko@sntech.de>,
"Johan Jonker" <jbx6244@gmail.com>,
linux-rockchip@lists.infradead.org,
"Kongxin Deng" <dkx@t-chip.com.cn>,
devicetree@vger.kernel.org, "Chen-Yu Tsai" <wens@csie.org>,
"David Bauer" <mail@david-bauer.net>,
"Krzysztof Kozlowski" <krzk@kernel.org>
Subject: Re: [PATCH v0 1/2] dt-bindings: add doc for Firefly ROC-RK3399-PC-PLUS
Date: Wed, 14 Jul 2021 14:52:25 -0600 [thread overview]
Message-ID: <20210714205225.GA3501265@robh.at.kernel.org> (raw)
In-Reply-To: <20210628035402.16812-2-djw@t-chip.com.cn>
On Mon, 28 Jun 2021 11:54:01 +0800, djw@t-chip.com.cn wrote:
> From: Levin Du <djw@t-chip.com.cn>
>
> Add devicetree binding documentation for the Firefly ROC-RK3399-PC-PLUS.
>
> Signed-off-by: Levin Du <djw@t-chip.com.cn>
> ---
>
> Documentation/devicetree/bindings/arm/rockchip.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-14 23:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 3:54 [PATCH v0 0/2] Add support for Firefly ROC-RK3399-PC-PLUS djw
2021-06-28 3:54 ` [PATCH v0 1/2] dt-bindings: add doc " djw
2021-07-14 20:52 ` Rob Herring [this message]
2021-06-28 3:54 ` [PATCH v0 2/2] arm64: dts: rockchip: add support " djw
2021-06-29 9:15 ` Levin
2021-06-29 9:30 ` Heiko Stübner
2021-06-29 9:32 ` Heiko Stübner
2021-06-30 6:49 ` Levin
2021-07-15 22:42 ` [PATCH v0 0/2] Add " Heiko Stuebner
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=20210714205225.GA3501265@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=djw@t-chip.com.cn \
--cc=dkx@t-chip.com.cn \
--cc=heiko@sntech.de \
--cc=jagan@amarulasolutions.com \
--cc=jbx6244@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mail@david-bauer.net \
--cc=robh+dt@kernel.org \
--cc=uwe@kleine-koenig.org \
--cc=wens@csie.org \
--cc=zxf@t-chip.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).