From: Brian Norris <briannorris@chromium.org>
To: Jianqun Xu <jay.xu@rock-chips.com>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
catalin.marinas@arm.com, will.deacon@arm.com, heiko@sntech.de,
huangtao@rock-chips.com, davidriley@chromium.org,
dianders@chromium.org, jwerner@chromium.org,
smbarber@chromium.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH RESEND v2 3/4] ARM64: dts: rockchip: add RK3399 evaluation board
Date: Mon, 25 Apr 2016 16:22:23 -0700 [thread overview]
Message-ID: <20160425232223.GA59576@google.com> (raw)
In-Reply-To: <1461304307-14113-4-git-send-email-jay.xu@rock-chips.com>
On Fri, Apr 22, 2016 at 01:51:46PM +0800, Jianqun Xu wrote:
> The RK3399 evaluation board is designed with pmic
> rk808 on top board.
>
> Signed-off-by: Jianqun Xu <jay.xu@rock-chips.com>
> ---
> changes in v2:
> - new add patch
FWIW, the $subject is a bit confusing. Probaly should be "Documentation:
...". But otherwise, LGTM.
next prev parent reply other threads:[~2016-04-25 23:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 5:51 [PATCH RESEND v2 0/4] ARM64: dts: rockchip: add support for RK3399 Jianqun Xu
2016-04-22 5:51 ` [PATCH RESEND v2 1/4] Documentation: rockchip-dw-mshc: add description for rk3399 Jianqun Xu
[not found] ` <1461304307-14113-2-git-send-email-jay.xu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-04-22 20:32 ` Rob Herring
2016-04-22 5:51 ` [PATCH RESEND v2 2/4] ARM64: dts: rockchip: add core dtsi file for RK3399 SoCs Jianqun Xu
2016-04-25 23:24 ` Brian Norris
[not found] ` <1461304307-14113-1-git-send-email-jay.xu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-04-22 5:51 ` [PATCH RESEND v2 3/4] ARM64: dts: rockchip: add RK3399 evaluation board Jianqun Xu
[not found] ` <1461304307-14113-4-git-send-email-jay.xu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-04-22 20:33 ` Rob Herring
2016-04-25 23:22 ` Brian Norris [this message]
2016-04-26 1:22 ` jay.xu
[not found] ` <20160425232223.GA59576-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2016-04-26 1:30 ` jay.xu
2016-04-22 5:51 ` [PATCH RESEND v2 4/4] ARM64: dts: rockchip: add dts file for " Jianqun Xu
[not found] ` <1461304307-14113-5-git-send-email-jay.xu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-04-25 1:47 ` Caesar Wang
[not found] ` <571D7723.1020707-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-04-25 7:37 ` Heiko Stübner
2016-04-25 22:23 ` Doug Anderson
2016-04-26 1:27 ` jay.xu
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=20160425232223.GA59576@google.com \
--to=briannorris@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=davidriley@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jay.xu@rock-chips.com \
--cc=jwerner@chromium.org \
--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=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=smbarber@chromium.org \
--cc=will.deacon@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).