From: kishon@ti.com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] phy: Group vendor specific phy drivers
Date: Thu, 28 Apr 2016 10:28:54 +0530 [thread overview]
Message-ID: <5721988E.7000105@ti.com> (raw)
In-Reply-To: <CAFp+6iHGSuTGbyWv4dV3GCNr=7VDRnBpcodwnoeB1i0zocUg5g@mail.gmail.com>
Hi,
On Tuesday 26 April 2016 11:36 AM, Vivek Gautam wrote:
> Hi Kishon,
>
>
> On Wed, Apr 6, 2016 at 7:37 PM, Vivek Gautam <gautam.vivek@samsung.com> wrote:
>> Adding vendor specific directories in phy to group
>> phy drivers under their respective vendor umbrella.
>>
>> Also updated the MAINTAINERS file to reflect the correct
>> directory structure for phy drivers.
>>
>> Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com>
>> Acked-by: Heiko Stuebner <heiko@sntech.de>
>> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>> ---
>>
>> Changes from v1:
>> - Updated the MAINTAINERS file to reflect the same change
>> in directory structure.
>> - Removed PHY_PLAT config as pointed out by Kishon.
>> So we don't require the second patch in the v1 of this series:
>> [PATCH 2/2] arm: mach-spear: Enable PHY_PLAT to meet dependency
>> - Renamed sunxi --> allwinner; rcar --> renesas.
>> - Fixed error coming with qcom Makefile.
>
> Does this change looks okay now ?
> I think you must be planning to take this in after 4.7 rc1 is out, isn't it ?
I'm not sure. I'm thinking which should be the right way to group the phy
drivers, by vendors or by type (usb, pcie, etc..). I'm more inclined to group
it by type.
Thanks
Kishon
next prev parent reply other threads:[~2016-04-28 4:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 14:07 [PATCH 1/2] phy: Move ULPI phy header out of driver to includes path Vivek Gautam
2016-04-06 14:07 ` [PATCH v2 2/2] phy: Group vendor specific phy drivers Vivek Gautam
2016-04-26 6:06 ` Vivek Gautam
2016-04-28 4:58 ` Kishon Vijay Abraham I [this message]
2016-04-28 5:25 ` Vivek Gautam
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=5721988E.7000105@ti.com \
--to=kishon@ti.com \
--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