devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
	devicetree@vger.kernel.org, mark.rutland@arm.com,
	christoph.muellner@theobroma-systems.com, robin.murphy@arm.com,
	heiko@sntech.de, linux-arm-kernel@lists.infradead.org,
	kever.yang@rock-chips.com, linux-kernel@vger.kernel.org,
	jbx6244@gmail.com,
	Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
Subject: Re: [PATCH v2 2/3] dt-bindings: Add binding for Hardkernel Odroid Go Advance
Date: Mon, 23 Mar 2020 13:55:31 -0600	[thread overview]
Message-ID: <20200323195531.GA6201@bogus> (raw)
In-Reply-To: <20200308223250.353053-2-heiko@sntech.de>

On Sun,  8 Mar 2020 23:32:49 +0100, Heiko Stuebner wrote:
> From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> 
> Add a compatible for the Odroid Go Advance from Hardkernel.
> The compatible used by the vendor already is odroid-go2, to distinguish
> it from the previous (microcontroller-based) Odroid Go, so we're keeping
> that, also to not cause unnecessary incompatibilites.
> 
> Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> ---
>  Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
>  1 file changed, 5 insertions(+)
> 

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

  reply	other threads:[~2020-03-23 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-08 22:32 [PATCH v2 1/3] arm64: dts: rockchip: add core devicetree for rk3326 Heiko Stuebner
2020-03-08 22:32 ` [PATCH v2 2/3] dt-bindings: Add binding for Hardkernel Odroid Go Advance Heiko Stuebner
2020-03-23 19:55   ` Rob Herring [this message]
2020-03-08 22:32 ` [PATCH v2 3/3] arm64: dts: rockchip: add Odroid Advance Go Heiko Stuebner
2020-03-08 22:39   ` 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=20200323195531.GA6201@bogus \
    --to=robh@kernel.org \
    --cc=christoph.muellner@theobroma-systems.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko.stuebner@theobroma-systems.com \
    --cc=heiko@sntech.de \
    --cc=jbx6244@gmail.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.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;
as well as URLs for NNTP newsgroup(s).