devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Frank Wunderlich <linux@fw-web.de>
Cc: linux-rockchip@lists.infradead.org,
	Johan Jonker <jbx6244@gmail.com>,
	devicetree@vger.kernel.org,
	Frank Wunderlich <frank-w@public-files.de>,
	Rob Herring <robh+dt@kernel.org>,
	linux-kernel@vger.kernel.org, Peter Geis <pgwipeout@gmail.com>,
	Heiko Stuebner <heiko@sntech.de>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] dt-bindings: rockchip: Add BananaPi R2 Pro Board
Date: Mon, 7 Feb 2022 16:56:26 -0600	[thread overview]
Message-ID: <YgGjmtyvioH8Vjrt@robh.at.kernel.org> (raw)
In-Reply-To: <20220123135116.136846-2-linux@fw-web.de>

On Sun, 23 Jan 2022 14:51:15 +0100, Frank Wunderlich wrote:
> From: Frank Wunderlich <frank-w@public-files.de>
> 
> Add Devicetree Binding for Bananapi R2 Pro Board based on rk3568 SoC
> 
> Co-developed-by: Peter Geis <pgwipeout@gmail.com>
> Signed-off-by: Peter Geis <pgwipeout@gmail.com>
> Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
> ---
>  Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
>  1 file changed, 5 insertions(+)
> 

Acked-by: Rob Herring <robh@kernel.org>

  parent reply	other threads:[~2022-02-08  1:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23 13:51 [PATCH v2 0/2] Add BananaPi R2 Pro board Frank Wunderlich
2022-01-23 13:51 ` [PATCH v2 1/2] dt-bindings: rockchip: Add BananaPi R2 Pro Board Frank Wunderlich
2022-02-05 18:59   ` Aw: " Frank Wunderlich
2022-02-07 22:56   ` Rob Herring [this message]
2022-01-23 13:51 ` [PATCH v2 2/2] arm64: dts: rockchip: Add Bananapi R2 Pro Frank Wunderlich
2022-01-24  8:31   ` Sascha Hauer
2022-01-24  8:55     ` Aw: " Frank Wunderlich
2022-01-24 11:03       ` Sascha Hauer
2022-01-24 11:49         ` Aw: " Frank Wunderlich
2022-02-08 16:59 ` [PATCH v2 0/2] Add BananaPi R2 Pro board 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=YgGjmtyvioH8Vjrt@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frank-w@public-files.de \
    --cc=heiko@sntech.de \
    --cc=jbx6244@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux@fw-web.de \
    --cc=pgwipeout@gmail.com \
    --cc=robh+dt@kernel.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).