[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR0402MB38714D71435CC4DF99AE5A20E0730@VI1PR0402MB3871.eurprd04.prod.outlook.com>
Date: Tue, 28 Jul 2020 16:28:31 +0000
From: Ioana Ciornei <ioana.ciornei@....com>
To: Andrew Lunn <andrew@...n.ch>
CC: netdev <netdev@...r.kernel.org>,
Florian Fainelli <f.fainelli@...il.com>,
Russell King <rmk+kernel@...linux.org.uk>,
Heiner Kallweit <hkallweit1@...il.com>
Subject: RE: [PATCH RFC net-next 0/3] Restructure drivers/net/phy
> 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
Powered by blists - more mailing lists