From: Rob Herring <robh@kernel.org>
To: Samuel Holland <samuel@sholland.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Levin Du <djw@t-chip.com.cn>,
Peter Geis <pgwipeout@gmail.com>, Liang Chen <cl@rock-chips.com>,
Rob Herring <robh+dt@kernel.org>,
linux-rockchip@lists.infradead.org,
Tianling Shen <cnsztl@gmail.com>,
Chen-Yu Tsai <wenst@chromium.org>,
Heiko Stuebner <heiko@sntech.de>, Alex Bee <knaerzche@gmail.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: arm: rockchip: Add Pine64 PineNote board
Date: Fri, 11 Feb 2022 07:25:51 -0600 [thread overview]
Message-ID: <YgZj3xeLvO1vA5+f@robh.at.kernel.org> (raw)
In-Reply-To: <20220130053803.43660-1-samuel@sholland.org>
On Sat, 29 Jan 2022 23:38:01 -0600, Samuel Holland wrote:
> The PineNote is a tablet from Pine64 based on the RK3566 SoC. There are
> two existing variants of the board. v1.1 was contained in some early
> samples, and v1.2 was sold as the "PineNote Developer Edition".
>
> Signed-off-by: Samuel Holland <samuel@sholland.org>
> ---
>
> Documentation/devicetree/bindings/arm/rockchip.yaml | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-02-11 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 5:38 [PATCH 1/3] dt-bindings: arm: rockchip: Add Pine64 PineNote board Samuel Holland
2022-01-30 5:38 ` [PATCH 2/3] arm64: dts: rockchip: rk356x: Add pdm node Samuel Holland
2022-01-30 9:49 ` Michael Riesch
2022-01-30 5:38 ` [PATCH 3/3] arm64: dts: rockchip: Add Pine64 PineNote board Samuel Holland
2022-02-02 10:41 ` Johan Jonker
2022-02-02 11:01 ` Johan Jonker
2022-02-11 13:25 ` Rob Herring [this message]
2022-02-12 0:23 ` [PATCH 1/3] dt-bindings: arm: " 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=YgZj3xeLvO1vA5+f@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=cl@rock-chips.com \
--cc=cnsztl@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=djw@t-chip.com.cn \
--cc=heiko@sntech.de \
--cc=knaerzche@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wenst@chromium.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;
as well as URLs for NNTP newsgroup(s).