linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Emmanuel Vadot <manu@freebsd.org>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, heiko@sntech.de,
	dianders@chromium.org, andy.yan@rock-chips.com,
	robin.murphy@arm.com, mka@chromium.org,
	jagan@amarulasolutions.com, nick@khadas.com,
	kever.yang@rock-chips.com, m.reichl@fivetechno.de,
	aballier@gentoo.org, pbrobinson@gmail.com, vicencb@gmail.com,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Emmanuel Vadot <manu@freebsd.org>
Subject: Re: [PATCH 1/2] dt-bindings: Add doc for Pine64 Pinebook Pro
Date: Wed, 22 Jan 2020 10:08:22 -0600	[thread overview]
Message-ID: <20200122160822.GA15049@bogus> (raw)
In-Reply-To: <20200116225617.6318-1-manu@freebsd.org>

On Thu, 16 Jan 2020 23:56:16 +0100, Emmanuel Vadot wrote:
> Add a compatible for Pine64 Pinebook Pro
> 
> Signed-off-by: Emmanuel Vadot <manu@freebsd.org>
> ---
>  Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
>  1 file changed, 5 insertions(+)
> 

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

  parent reply	other threads:[~2020-01-22 16:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 22:56 [PATCH 1/2] dt-bindings: Add doc for Pine64 Pinebook Pro Emmanuel Vadot
2020-01-16 22:56 ` [PATCH 2/2] arm64: dts: rockchip: Add initial support for " Emmanuel Vadot
2020-01-19 20:17   ` Heiko Stübner
2020-01-19 21:31     ` Emmanuel Vadot
2020-01-21 14:13   ` Tobias Schramm
2020-01-21 14:21     ` Heiko Stuebner
2020-01-20 11:24 ` [PATCH 1/2] dt-bindings: Add doc for Pine64 " Johan Jonker
2020-01-22 16:08 ` Rob Herring [this message]
2020-02-27 18:06 [PATCH 0/2] Add support for the pine64 " Tobias Schramm
2020-02-27 18:06 ` [PATCH 1/2] dt-bindings: Add doc for " Tobias Schramm

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=20200122160822.GA15049@bogus \
    --to=robh@kernel.org \
    --cc=aballier@gentoo.org \
    --cc=andy.yan@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=heiko@sntech.de \
    --cc=jagan@amarulasolutions.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=m.reichl@fivetechno.de \
    --cc=manu@freebsd.org \
    --cc=mark.rutland@arm.com \
    --cc=mka@chromium.org \
    --cc=nick@khadas.com \
    --cc=pbrobinson@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=vicencb@gmail.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).