[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20231123144441.3d73bf51@device.home>
Date: Thu, 23 Nov 2023 14:44:41 +0100
From: Maxime Chevallier <maxime.chevallier@...tlin.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: davem@...emloft.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, thomas.petazzoni@...tlin.com, Jakub Kicinski
<kuba@...nel.org>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, Russell King <linux@...linux.org.uk>,
linux-arm-kernel@...ts.infradead.org, Christophe Leroy
<christophe.leroy@...roup.eu>, Herve Codina <herve.codina@...tlin.com>,
Florian Fainelli <f.fainelli@...il.com>, Heiner Kallweit
<hkallweit1@...il.com>, Vladimir Oltean <vladimir.oltean@....com>,
Köry Maincent <kory.maincent@...tlin.com>, Jesse Brandeburg
<jesse.brandeburg@...el.com>
Subject: Re: [RFC PATCH net-next v2 01/10] net: phy: Introduce ethernet link
topology representation
On Tue, 21 Nov 2023 01:24:47 +0100
Andrew Lunn <andrew@...n.ch> wrote:
[...]
>
> > diff --git a/include/linux/link_topology.h b/include/linux/link_topology.h
>
> I think this filename is too generic. Maybe phy_link_topology.h, or
> move it into include/net.
Yeah naming again, phy_link_topology would make sense indeed. I know
that Florian suggested phy_devices_list last time, However I'd like
this to be more than just about PHYs, to keep track of ports, mii-muxes
and such. So, phy_link_topology sounds good to me :)
Maxime
Powered by blists - more mailing lists