From: Doug Berger <opendmb@gmail.com>
To: Ioana Ciornei <ioana.ciornei@nxp.com>, Andrew Lunn <andrew@lunn.ch>
Cc: netdev <netdev@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Russell King <rmk+kernel@armlinux.org.uk>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH RFC net-next 0/3] Restructure drivers/net/phy
Date: Tue, 28 Jul 2020 17:28:42 -0700 [thread overview]
Message-ID: <1c484c7b-1988-20dc-9433-3f322e81280c@gmail.com> (raw)
In-Reply-To: <VI1PR0402MB38714D71435CC4DF99AE5A20E0730@VI1PR0402MB3871.eurprd04.prod.outlook.com>
On 7/28/2020 9:28 AM, Ioana Ciornei wrote:
>> Subject: Re: [PATCH RFC net-next 0/3] Restructure drivers/net/phy
>>
>>> I think that the MAINTAINERS file should also be updated to mention
>>> the new path to the drivers. Just did a quick grep after 'drivers/net/phy':
>>> F: drivers/net/phy/adin.c
>>> F: drivers/net/phy/mdio-xgene.c
>>> F: drivers/net/phy/
>>> F: drivers/net/phy/marvell10g.c
>>> F: drivers/net/phy/mdio-mvusb.c
>>> F: drivers/net/phy/dp83640*
>>> F: drivers/net/phy/phylink.c
>>> F: drivers/net/phy/sfp*
>>> F: drivers/net/phy/mdio-xpcs.c
>>
>> Hi Ioana
>>
>> Thanks, I will take care of that.
>>
>>> Other than that, the new 'drivers/net/phy/phy/' path is somewhat
>>> repetitive but unfortunately I do not have another better suggestion.
>>
>> Me neither.
>>
>> I wonder if we are looking at the wrong part of the patch.
>> drivers/net/X/phy/
>> drivers/net/X/mdio/
>> drivers/net/X/pcs/
>>
>> Question is, what would X be?
>>
>> Andrew
>
> It may not be a popular suggestion but can't we take the drivers/net/phy,
> drivers/net/pcs and drivers/net/mdio route?
>
> Ioana
>
>
>
That sounds preferable to me as well.
-Doug
next prev parent reply other threads:[~2020-07-29 0:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 20:47 [PATCH RFC net-next 0/3] Restructure drivers/net/phy Andrew Lunn
2020-07-27 20:47 ` [PATCH RFC net-next 1/3] net: xgene: Move shared header file into include/linux Andrew Lunn
2020-07-27 20:47 ` [PATCH RFC net-next 2/3] net: phy: Move into subdirectories Andrew Lunn
2020-08-03 14:11 ` Madalin Bucur (OSS)
2020-08-03 14:15 ` Andrew Lunn
2020-07-27 20:47 ` [PATCH RFC net-next 3/3] net: phy: Move and rename mdio-xpcs Andrew Lunn
2020-07-27 22:05 ` [PATCH RFC net-next 0/3] Restructure drivers/net/phy Jakub Kicinski
2020-07-27 22:20 ` Andrew Lunn
2020-07-28 15:42 ` Ioana Ciornei
2020-07-28 15:55 ` Russell King - ARM Linux admin
2020-07-28 16:08 ` Andrew Lunn
2020-07-28 16:28 ` Ioana Ciornei
2020-07-29 0:28 ` Doug Berger [this message]
2020-07-29 0:34 ` Florian Fainelli
2020-07-31 1:25 ` Andrew Lunn
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=1c484c7b-1988-20dc-9433-3f322e81280c@gmail.com \
--to=opendmb@gmail.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
/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).