From: briannorris@chromium.org (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: dts: rockchip: add veyron-brain board
Date: Wed, 2 Dec 2015 10:26:23 -0800 [thread overview]
Message-ID: <20151202182623.GA49625@google.com> (raw)
In-Reply-To: <6340149.qAGjxgRvNd@diego>
On Tue, Dec 01, 2015 at 06:16:02PM +0100, Heiko St?bner wrote:
> Similar to pinky, brain is a development model and probably also
> nearing extinction. But to keep pinky from being lonely I'll keep
> the two brain boards around as well, especially as they as well
> have easily accessible dut-connectors.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@collabora.com>
> ---
> would cool to get an Ack from ChromeOS-people concerning the
> license change to GPL2/X11 - as with the dts before
For the license changes:
Acked-by: Brian Norris <briannorris@chromium.org>
Not tested or reviewed otherwise.
> Documentation/devicetree/bindings/arm/rockchip.txt | 5 +
> arch/arm/boot/dts/Makefile | 1 +
> arch/arm/boot/dts/rk3288-veyron-brain.dts | 139 +++++++++++++++++++++
> 3 files changed, 145 insertions(+)
> create mode 100644 arch/arm/boot/dts/rk3288-veyron-brain.dts
...
Brian
next prev parent reply other threads:[~2015-12-02 18:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 17:14 [PATCH 1/3] ARM: dts: rockchip: make sure edp_24m is associated to xin24m on veyron Heiko Stübner
2015-12-01 17:16 ` [PATCH 2/3] ARM: dts: rockchip: add veyron-brain board Heiko Stübner
2015-12-02 18:26 ` Brian Norris [this message]
2015-12-01 17:16 ` [PATCH 3/3] ARM: dts: rockchip: add veyron-minnie board Heiko Stübner
2015-12-01 17:19 ` Heiko Stübner
2015-12-02 18:31 ` Brian Norris
2015-12-03 10:27 ` Caesar Wang
2015-12-03 10:44 ` Heiko Stübner
2015-12-03 11:01 ` Caesar Wang
2015-12-03 14:00 ` Heiko Stübner
2015-12-03 15:43 ` [PATCH 1/3] ARM: dts: rockchip: make sure edp_24m is associated to xin24m on veyron Heiko Stübner
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=20151202182623.GA49625@google.com \
--to=briannorris@chromium.org \
--cc=linux-arm-kernel@lists.infradead.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).