From: Kishon Vijay Abraham I <kishon@ti.com>
To: Jaehoon Chung <jh80.chung@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <kgene@kernel.org>,
<kamil@wypas.org>, Sylwester Nawrocki <s.nawrocki@samsung.com>,
Javier Martinez Canillas <javier@osg.samsung.com>,
<linux-samsung-soc@vger.kernel.org>
Subject: Re: [RFC PATCH] phy: samsung: move the Samsung specific phy files to "samsung" directory
Date: Fri, 10 Mar 2017 15:19:38 +0530 [thread overview]
Message-ID: <58C276B2.9020707@ti.com> (raw)
In-Reply-To: <4b023d24-6d6b-94be-8895-7ff7f733e5b8@samsung.com>
Hi,
On Friday 10 March 2017 12:30 PM, Jaehoon Chung wrote:
> Hi All,
>
> On 03/09/2017 09:10 PM, Krzysztof Kozlowski wrote:
>> On Thu, Mar 9, 2017 at 1:56 PM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
>>> Hi,
>>>
>>> On Thursday 09 March 2017 05:03 PM, Jaehoon Chung wrote:
>>>> Make the "samsung" directory and move the Samsung specific files to
>>>> there for maintaining the files relevant to Samsung.
>>>
>>> The number of phy drivers in drivers/phy is getting unmanageable. I think this
>>> is a good step to make it a little better. Can you also add a MAINTAINER for
>>> drivers/phy/samsung?
>>
>> There is such:
>>
>> 10903 SAMSUNG USB2 PHY DRIVER
>> 10904 M: Kamil Debski <kamil@wypas.org>
>> 10905 M: Sylwester Nawrocki <s.nawrocki@samsung.com>
>> 10906 L: linux-kernel@vger.kernel.org
>> 10907 S: Supported
>> 10908 F: Documentation/devicetree/bindings/phy/samsung-phy.txt
>> 10909 F: Documentation/phy/samsung-usb2.txt
>> 10910 F: drivers/phy/phy-exynos4210-usb2.c
>> 10911 F: drivers/phy/phy-exynos4x12-usb2.c
>> 10912 F: drivers/phy/phy-exynos5250-usb2.c
>> 10913 F: drivers/phy/phy-s5pv210-usb2.c
>> 10914 F: drivers/phy/phy-samsung-usb2.c
>> 10915 F: drivers/phy/phy-samsung-usb2.h
>>
>> but this patchset does not update it. Paths *everywhere* have to be updated.
>
> Will update..How about the below updating?
> M: Kamil Debski <kamil@wypas.org>
> M: Sylwester Nawrocki <s.nawrocki@samsung.com>
> M: Jaehoon Chung <jh80.chung@samsung.com>
> L: linux-kernel@vger.kernel.org
> S: Supported
> F: Documentation/devicetree/bindings/phy/samsung-phy.txt
> F: Documentation/phy/samsung-usb2.txt
> F: driver/phy/samsung/
>
> Let me know your opinion.
Looks good to me.
Thanks
Kishon
>
> Best Regards,
> Jaehoon Chung
>
>>
>> Best regards,
>> Krzysztof
>>
>>
>>
>
next prev parent reply other threads:[~2017-03-10 9:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170309113312epcas5p3eceb2a9cce9fc8ff6871bee7b45dc15e@epcas5p3.samsung.com>
2017-03-09 11:33 ` [RFC PATCH] phy: samsung: move the Samsung specific phy files to "samsung" directory Jaehoon Chung
2017-03-09 11:56 ` Kishon Vijay Abraham I
2017-03-09 12:10 ` Krzysztof Kozlowski
2017-03-10 7:00 ` Jaehoon Chung
2017-03-10 9:49 ` Kishon Vijay Abraham I [this message]
2017-03-10 17:55 ` Krzysztof Kozlowski
2017-03-12 9:18 ` Vivek Gautam
2017-03-12 9:23 ` Krzysztof Kozlowski
2017-03-12 17:20 ` Vivek Gautam
2017-03-12 23:18 ` Jaehoon Chung
2017-03-13 8:59 ` Vivek Gautam
2017-03-13 5:21 ` Kishon Vijay Abraham I
2017-03-13 8:57 ` Vivek Gautam
2017-03-13 9:01 ` Kishon Vijay Abraham I
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=58C276B2.9020707@ti.com \
--to=kishon@ti.com \
--cc=javier@osg.samsung.com \
--cc=jh80.chung@samsung.com \
--cc=kamil@wypas.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.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).