From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Simon Horman" <horms@kernel.org>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com,
"Jakub Kicinski" <kuba@kernel.org>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Russell King" <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Herve Codina" <herve.codina@bootlin.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Vladimir Oltean" <vladimir.oltean@nxp.com>,
"Köry Maincent" <kory.maincent@bootlin.com>,
"Jesse Brandeburg" <jesse.brandeburg@intel.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Marek Behún" <kabel@kernel.org>,
"Piergiorgio Beruto" <piergiorgio.beruto@gmail.com>,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
"Nicolò Veronese" <nicveronese@gmail.com>
Subject: Re: [RFC PATCH net-next v3 01/13] net: phy: Introduce ethernet link topology representation
Date: Tue, 12 Dec 2023 14:10:26 +0100 [thread overview]
Message-ID: <20231212141026.37e7af58@device.home> (raw)
In-Reply-To: <67557c83-4318-4557-ac96-858053b5f89b@lunn.ch>
On Mon, 11 Dec 2023 15:09:09 +0100
Andrew Lunn <andrew@lunn.ch> wrote:
> > > > @@ -10832,6 +10833,8 @@ struct net_device *alloc_netdev_mqs(int sizeof_priv, const char *name,
> > > > #ifdef CONFIG_NET_SCHED
> > > > hash_init(dev->qdisc_hash);
> > > > #endif
> > > > + phy_link_topo_init(&dev->link_topo);
> > > > +
> > >
> > > I don't think this can work unless PHYLIB is compiled as a built-in.
> >
> > Inded, I need to better clarify and document the dependency with
> > PHYLIB.
>
> It is getting harder and harder to make the phylib core a module :-(
>
> How much work does phy_link_topo_init() do? Could it be an inline
> function? Are there other dependencies?
Sorry about that, I'll make sure it works with phylib entirely disabled
for next version. I try to keep the integration with net_device minimal
and avoid any dependency bloat, we don't need much besides xarray stuff
(hence the fact there are 2 headers, the phy_link_topology_core.h
containing the bare minimum), but I did miss that.
> Also look at ethtool_phy_ops and e.g. how plca_get_cfg_prepare_data()
> uses it.
Thanks, indeed that's a good example. I'll also address that in the
netlink part as well.
Thanks,
Maxime
next prev parent reply other threads:[~2023-12-12 13:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 16:36 [RFC PATCH net-next v3 00/13] Introduce PHY listing and link_topology tracking Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 01/13] net: phy: Introduce ethernet link topology representation Maxime Chevallier
2023-12-09 17:02 ` Simon Horman
2023-12-11 11:06 ` Maxime Chevallier
2023-12-11 14:09 ` Andrew Lunn
2023-12-12 13:10 ` Maxime Chevallier [this message]
2023-12-01 16:36 ` [RFC PATCH net-next v3 02/13] net: sfp: pass the phy_device when disconnecting an sfp module's PHY Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 03/13] net: phy: add helpers to handle sfp phy connect/disconnect Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 04/13] net: sfp: Add helper to return the SFP bus name Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 05/13] net: ethtool: Allow passing a phy index for some commands Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 06/13] netlink: specs: add phy-index as a header parameter Maxime Chevallier
2023-12-04 10:36 ` Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 07/13] net: ethtool: Introduce a command to list PHYs on an interface Maxime Chevallier
2023-12-09 17:04 ` Simon Horman
2023-12-11 11:07 ` Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 08/13] netlink: specs: add ethnl PHY_GET command set Maxime Chevallier
2023-12-04 10:37 ` Maxime Chevallier
2023-12-01 16:36 ` [RFC PATCH net-next v3 09/13] net: ethtool: plca: Target the command to the requested PHY Maxime Chevallier
2023-12-01 16:37 ` [RFC PATCH net-next v3 10/13] net: ethtool: pse-pd: " Maxime Chevallier
2023-12-01 16:37 ` [RFC PATCH net-next v3 11/13] net: ethtool: cable-test: " Maxime Chevallier
2023-12-01 16:37 ` [RFC PATCH net-next v3 12/13] net: ethtool: strset: Allow querying phy stats by index Maxime Chevallier
2023-12-01 16:37 ` [RFC PATCH net-next v3 13/13] Documentation: networking: document phy_link_topology Maxime Chevallier
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=20231212141026.37e7af58@device.home \
--to=maxime.chevallier@bootlin.com \
--cc=andrew@lunn.ch \
--cc=christophe.leroy@csgroup.eu \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=herve.codina@bootlin.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=jesse.brandeburg@intel.com \
--cc=kabel@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=nicveronese@gmail.com \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=piergiorgio.beruto@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.oltean@nxp.com \
/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).