From: briannorris@chromium.org (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/4] dt-bindings: Document rk3399 Gru/Kevin
Date: Wed, 22 Mar 2017 10:56:37 -0700 [thread overview]
Message-ID: <20170322175636.GA98450@google.com> (raw)
In-Reply-To: <3700058.o6cBinDvsr@phil>
On Wed, Mar 22, 2017 at 10:01:00AM +0100, Heiko Stuebner wrote:
> Am Montag, 20. M?rz 2017, 16:53:41 CET schrieb Brian Norris:
> > Gru is a base dev board for a family of devices, including Kevin. Both
> > utilize Rockchip RK3399, and they share much of their design.
> >
> > Signed-off-by: Brian Norris <briannorris@chromium.org>
> > Acked-by: Rob Herring <robh@kernel.org>
>
> applied for 4.12, after adding a "(Samsung Chromebook Plus)" hint, as that may
> help people identifying the correct dts and also is public knowledge (some
> blogs but also /proc/device-tree/compatible on the device itself).
Oh, thanks. There wasn't a public name when I first started sending this
series :)
Brian
next prev parent reply other threads:[~2017-03-22 17:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 23:53 [PATCH v3 0/4] arm64: dts: rockchip: support Google Kevin Brian Norris
2017-03-20 23:53 ` [PATCH v3 1/4] dt-bindings: Document rk3399 Gru/Kevin Brian Norris
2017-03-22 9:01 ` Heiko Stuebner
2017-03-22 17:56 ` Brian Norris [this message]
2017-03-20 23:53 ` [PATCH v3 2/4] arm64: dts: rockchip: add Gru/Kevin DTS Brian Norris
2017-03-21 11:02 ` Enric Balletbo Serra
2017-03-22 11:59 ` Heiko Stuebner
2017-03-22 17:57 ` Brian Norris
2017-03-20 23:53 ` [PATCH v3 3/4] arm64: dts: rockchip: describe Gru/Kevin OPPs + CPU regulators Brian Norris
2017-03-21 11:04 ` Enric Balletbo Serra
2017-03-22 12:00 ` Heiko Stuebner
2017-03-20 23:53 ` [PATCH v3 4/4] arm64: dts: rockchip: add regulator info for Kevin digitizer Brian Norris
2017-03-22 8:26 ` Heiko Stuebner
2017-03-22 18:14 ` Brian Norris
2017-03-22 23:57 ` 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=20170322175636.GA98450@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).