[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d3ded8c2-33c4-96fa-59f1-47dbc5b7e165@ti.com>
Date: Wed, 7 Jun 2017 19:09:21 +0530
From: Kishon Vijay Abraham I <kishon@...com>
To: Florian Fainelli <f.fainelli@...il.com>,
Raviteja Garimella <raviteja.garimella@...adcom.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....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 Friday 02 June 2017 09:23 PM, Florian Fainelli wrote:
>
>
> 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
+1
-Kishon
Powered by blists - more mailing lists