From: Heiko Stuebner <heiko@sntech.de>
To: Brian Norris <briannorris@chromium.org>
Cc: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Caesar Wang <wxt@rock-chips.com>,
Doug Anderson <dianders@chromium.org>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Stephen Barber <smbarber@chromium.org>,
linux-arm-kernel@lists.infradead.org,
Chris Zhong <zyw@rock-chips.com>
Subject: Re: [PATCH v2 2/6] arm64: dts: rockchip: support dwc3 USB for rk3399
Date: Fri, 10 Feb 2017 23:01:54 +0100 [thread overview]
Message-ID: <2384713.Q7s8nQmdof@phil> (raw)
In-Reply-To: <20170210010521.78872-3-briannorris@chromium.org>
Am Donnerstag, 9. Februar 2017, 17:05:17 CET schrieb Brian Norris:
> Add the dwc3 usb needed node information for rk3399.
>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
applied for 4.12
Thanks
Heiko
next prev parent reply other threads:[~2017-02-10 22:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 1:05 [PATCH v2 0/6] arm64: dts: rockchip: support Google Kevin Brian Norris
2017-02-10 1:05 ` [PATCH v2 1/6] arm64: dts: Add symlinks for cros-ec-keyboard and cros-ec-sbs Brian Norris
2017-02-21 23:47 ` Olof Johansson
2017-02-27 18:20 ` Heiko Stuebner
2017-03-20 23:07 ` Brian Norris
2017-04-19 12:54 ` Olof Johansson
2017-04-19 13:25 ` Heiko Stuebner
2017-04-19 13:31 ` Olof Johansson
2017-02-10 1:05 ` [PATCH v2 2/6] arm64: dts: rockchip: support dwc3 USB for rk3399 Brian Norris
2017-02-10 22:01 ` Heiko Stuebner [this message]
2017-02-10 1:05 ` [PATCH v2 3/6] dt-bindings: Document rk3399 Gru/Kevin Brian Norris
2017-02-16 2:12 ` Rob Herring
2017-02-10 1:05 ` [PATCH v2 4/6] arm64: dts: rockchip: add Gru/Kevin DTS Brian Norris
2017-02-28 22:00 ` Heiko Stuebner
2017-02-28 22:54 ` Doug Anderson
2017-02-10 1:05 ` [PATCH v2 5/6] arm64: dts: rockchip: describe Gru/Kevin OPPs + CPU regulators Brian Norris
2017-02-10 1:05 ` [PATCH v2 6/6] arm64: dts: rockchip: sort rk3399 by unit address Brian Norris
2017-02-10 21: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=2384713.Q7s8nQmdof@phil \
--to=heiko@sntech.de \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=smbarber@chromium.org \
--cc=wxt@rock-chips.com \
--cc=zyw@rock-chips.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).