From: Florian Fainelli <f.fainelli@gmail.com>
To: Raviteja Garimella <raviteja.garimella@broadcom.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Jon Mason <jonmason@broadcom.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v8 3/3] arm64: dts: NS2: Add USB DRD PHY device tree node
Date: Thu, 8 Jun 2017 13:57:00 -0700 [thread overview]
Message-ID: <84aa2a67-3326-1a0a-c42f-23ef93306ed0@gmail.com> (raw)
In-Reply-To: <1496918103-14948-4-git-send-email-raviteja.garimella@broadcom.com>
On 06/08/2017 03:35 AM, Raviteja Garimella wrote:
> This patch adds device tree node for USB Dual Role Device PHY for
> Broadcom's Northstar2 SoC.
>
> Signed-off-by: Raviteja Garimella <raviteja.garimella@broadcom.com>
Since Rob acked the binding, applied to devicetree-arm64/next, thanks
--
--
Florian
next prev parent reply other threads:[~2017-06-08 20:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 10:35 [PATCH v8 0/3] Support for USB DRD PHY driver for NS2 Raviteja Garimella
2017-06-08 10:35 ` [PATCH v8 1/3] dt-bindings: phy: Add DT bindings documentation for NS2 USB DRD PHY Raviteja Garimella
2017-06-08 10:35 ` [PATCH v8 2/3] phy: phy-bcm-ns2-usbdrd: Broadcom USB DRD PHY driver for Northstar2 Raviteja Garimella
2017-06-08 10:35 ` [PATCH v8 3/3] arm64: dts: NS2: Add USB DRD PHY device tree node Raviteja Garimella
2017-06-08 20:57 ` Florian Fainelli [this message]
2017-06-09 8:55 ` [PATCH v8 0/3] Support for USB DRD PHY driver for NS2 Kishon Vijay Abraham I
2017-06-09 9:00 ` Raviteja Garimella
2017-06-09 9:06 ` Kishon Vijay Abraham I
2017-06-09 10:53 ` Raviteja Garimella
2017-06-09 11:16 ` Kishon Vijay Abraham I
2017-06-09 11:36 ` Raviteja Garimella
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=84aa2a67-3326-1a0a-c42f-23ef93306ed0@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jonmason@broadcom.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=raviteja.garimella@broadcom.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--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).