netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: Andrew Lunn <andrew@lunn.ch>, netdev <netdev@vger.kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH RFC net-next 0/3] Restructure drivers/net/phy
Date: Tue, 28 Jul 2020 16:55:20 +0100	[thread overview]
Message-ID: <20200728155520.GS1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <VI1PR0402MB3871906F6381418258CC7AEBE0730@VI1PR0402MB3871.eurprd04.prod.outlook.com>

On Tue, Jul 28, 2020 at 03:42:22PM +0000, Ioana Ciornei wrote:
> > Subject: [PATCH RFC net-next 0/3] Restructure drivers/net/phy
> > 
> > RFC Because it needs 0-day build testing
> > 
> > The directory drivers/net/phy is getting rather cluttered with the growing
> > number of MDIO bus drivers and PHY device drivers. We also have one PCS
> > driver and more are expected soon.
> > 
> > Restructure the directory, moving MDIO bus drivers into /mdio.  PHY drivers into
> > /phy. The one current PCS driver is moved into /pcs and renamed to give it the
> > pcs- prefix which we hope will be followed by other PCS drivers.
> > 
> 
> Other than that, the new 'drivers/net/phy/phy/' path is somewhat repetitive but
> unfortunately I do not have another better suggestion.

There aren't many suitable names.  The options I can think of are:

drivers	(but is still repetitive, or drv for a shortened version)
media	(since they're driving media facing PHYs)
phy	(as already suggested by Andrew)

Nothing really stands out as a good choice.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2020-07-28 15:55 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 [this message]
2020-07-28 16:08   ` Andrew Lunn
2020-07-28 16:28     ` Ioana Ciornei
2020-07-29  0:28       ` Doug Berger
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=20200728155520.GS1551@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=ioana.ciornei@nxp.com \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).