From: Kishon Vijay Abraham I <kishon@ti.com>
To: Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kukjin Kim <kgene@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>, <kamil@wypas.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Javier Martinez Canillas <javier@osg.samsung.com>,
<inux-samsung-soc@vger.kernel.org>
Subject: Re: [RFC PATCH] phy: samsung: move the Samsung specific phy files to "samsung" directory
Date: Mon, 13 Mar 2017 14:31:03 +0530 [thread overview]
Message-ID: <58C65FCF.4030207@ti.com> (raw)
In-Reply-To: <CAFp+6iGiWRO=ybDvf6R1Ai5YTjyYgTyWomixSY82Zocf-am4OA@mail.gmail.com>
Hi Vivek,
On Monday 13 March 2017 02:27 PM, Vivek Gautam wrote:
> Hi Kishon,
>
>
> On Mon, Mar 13, 2017 at 10:51 AM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
>> Hi,
>>
>> On Sunday 12 March 2017 02:48 PM, Vivek Gautam wrote:
>>> Hi Kishon,
>>>
>>>
>>> On Thu, Mar 9, 2017 at 5:26 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?
>>>
>>> I remember making a similar attempt in past [1], but that time we couldn't
>>> reach an agreement as to whether group the phy drivers based on
>>> vendors or based on the type of phy.
>>>
>>> If you are fine with grouping the drivers for each vendor, I hope you can
>>> consider picking that patch (I can respin the patch based on linux-phy/next).
>>> Other driver maintainers were also cool with that older patch.
>>
>> Sure, you can re-spin the patch.
>
> Thanks, will re-spin the patch.
>
>>
>> At that point of time I didn't think grouping phy drivers for each vendor is
>> required. But especially after [1] where I failed to notice an existing phy
>> driver can be reused and later has to be reverted. This could have been easily
>> identified by MAINTAINERS of that particular platform. That's why now I feel
>> grouping phy drivers and having a MAINTAINER for every vendor directory will
>> help to identify such issues.
>
> I will be able to update the MAINTAINERS file for the directory structure
> change only, like I did in my earlier version.
> We will have to ask each vendors to pull in vendors for each directory.
That's fine. Eventually we'll get that added.
Thanks
Kishon
prev parent reply other threads:[~2017-03-13 9:02 UTC|newest]
Thread overview: 15+ 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
2017-03-10 9:49 ` Kishon Vijay Abraham I
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 [this message]
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=58C65FCF.4030207@ti.com \
--to=kishon@ti.com \
--cc=inux-samsung-soc@vger.kernel.org \
--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=s.nawrocki@samsung.com \
--cc=vivek.gautam@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.