[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4824c415-ea31-f252-7e94-ed3e3b2c064c@gmail.com>
Date: Fri, 2 Jun 2017 08:53:19 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Raviteja Garimella <raviteja.garimella@...adcom.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Kishon Vijay Abraham I <kishon@...com>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
Jon Mason <jonmason@...adcom.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
bcm-kernel-feedback-list@...adcom.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v7 0/3] Support for USB DRD Phy driver for NS2
On 06/02/2017 06:00 AM, Raviteja Garimella wrote:
>
> Raviteja Garimella (3):
> dt-bindings:phy:Add DT bindings documentation for NS2 USB DRD phy
> phy:phy-bcm-ns2-usbdrd:Broadcom USB DRD Phy driver for Northstar2
> arm64: dts: NS2: Add USB DRD PHY device tree node
For future submission can you be consistent in how you create your
subjects and how PHY vs. Phy or phy is used? For instance this would be
much better:
dt-bindings: phy: Add DT bindings documentation for NS2 USB DRD PHY
phy: phy-bcm-ns2-usbdrd: Broadcom USB DRD PHY driver for Northstar 2
Thank you
--
Florian
Powered by blists - more mailing lists