public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: davem@davemloft.net, "Andrew Lunn" <andrew@lunn.ch>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Russell King" <linux@armlinux.org.uk>,
	"Heiner Kallweit" <hkallweit1@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	thomas.petazzoni@bootlin.com,
	"Christophe Leroy" <christophe.leroy@csgroup.eu>,
	"Herve Codina" <herve.codina@bootlin.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Vladimir Oltean" <vladimir.oltean@nxp.com>,
	"Köry Maincent" <kory.maincent@bootlin.com>,
	"Marek Behún" <kabel@kernel.org>,
	"Oleksij Rempel" <o.rempel@pengutronix.de>,
	"Nicolò Veronese" <nicveronese@gmail.com>,
	"Simon Horman" <horms@kernel.org>,
	mwojtas@chromium.org,
	"Romain Gantois" <romain.gantois@bootlin.com>,
	"Daniel Golle" <daniel@makrotopia.org>,
	"Dimitri Fedrau" <dimitri.fedrau@liebherr.com>
Subject: Re: [PATCH net-next v2 00/12] net: phy_port: SFP modules representation and phy_port listing
Date: Thu, 29 Jan 2026 19:59:55 -0800	[thread overview]
Message-ID: <20260129195955.3bbff4fd@kernel.org> (raw)
In-Reply-To: <20260128204526.170927-1-maxime.chevallier@bootlin.com>

On Wed, 28 Jan 2026 21:45:13 +0100 Maxime Chevallier wrote:
> Here's V2 of the second phy_port series, this time bringing support for
> more phy_port use especially for SFP, as well as the beggining of a
> ethnl uAPI. That's a quick repost, but with the build issues and AI
> review, I think it's worth getting this version out there for review.
> 
> It builds on the recent addition of phy_port representation to enable
> listing the front-facing ports of an interface. For now, we don't control
> these ports, we merely list their presence and their capabilities.
> 
> As the most common use-case of multi-port interfaces is combo-ports that
> provide both RJ45 and SFP connectors on a single MAC, there's a lot of
> SFP stuff in this series.
> 
> This series is in 2 main parts. The first one aims at representing the
> SFP cages and modules using phy_port, as combo-ports with RJ45 + SFP are
> by far the most common cases for multi-connector setups.
> 
> The second part is the netlink interface to list those ports, now that
> most use-cases are covered.

I'll send out the AI code review. The one on patch 9 looks plausible,
not sure about the rest. LMK if none of them in fact make sense.

  parent reply	other threads:[~2026-01-30  3:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28 20:45 [PATCH net-next v2 00/12] net: phy_port: SFP modules representation and phy_port listing Maxime Chevallier
2026-01-28 20:45 ` [PATCH net-next v2 01/12] net: phy: phy_port: Correctly recompute the port's linkmodes Maxime Chevallier
2026-01-30  4:00   ` [net-next,v2,01/12] " Jakub Kicinski
2026-01-28 20:45 ` [PATCH net-next v2 02/12] net: phy: phy_link_topology: Add a helper for opportunistic alloc Maxime Chevallier
2026-01-28 20:45 ` [PATCH net-next v2 03/12] net: phy: phy_link_topology: Track ports in phy_link_topology Maxime Chevallier
2026-01-30  4:00   ` [net-next,v2,03/12] " Jakub Kicinski
2026-01-28 20:45 ` [PATCH net-next v2 04/12] net: phylink: Register a phy_port for MAC-driven SFP busses Maxime Chevallier
2026-01-28 20:45 ` [PATCH net-next v2 05/12] net: phy: Create SFP phy_port before registering usptream Maxime Chevallier
2026-01-28 20:45 ` [PATCH net-next v2 06/12] net: sfp: Add a sfp-bus ops when connecting a module without PHY Maxime Chevallier
2026-01-28 20:45 ` [PATCH net-next v2 07/12] net: phy: Represent PHY-less SFP modules with phy_port Maxime Chevallier
2026-01-28 20:45 ` [PATCH net-next v2 08/12] net: phylink: " Maxime Chevallier
2026-01-30  4:00   ` [net-next,v2,08/12] " Jakub Kicinski
2026-01-28 20:45 ` [PATCH net-next v2 09/12] net: phy: phy_port: Store information about a MII port's occupancy Maxime Chevallier
2026-01-30  4:00   ` [net-next,v2,09/12] " Jakub Kicinski
2026-01-28 20:45 ` [PATCH net-next v2 10/12] net: phy: phy_link_topology: Add a helper to retrieve ports Maxime Chevallier
2026-01-28 20:45 ` [PATCH net-next v2 11/12] netlink: specs: Add ethernet port listing with ethtool Maxime Chevallier
2026-01-28 20:45 ` [PATCH net-next v2 12/12] net: ethtool: Introduce ethtool command to list ports Maxime Chevallier
2026-01-30  3:59 ` Jakub Kicinski [this message]
2026-01-30  8:21   ` [PATCH net-next v2 00/12] net: phy_port: SFP modules representation and phy_port listing 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=20260129195955.3bbff4fd@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=christophe.leroy@csgroup.eu \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=dimitri.fedrau@liebherr.com \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=herve.codina@bootlin.com \
    --cc=hkallweit1@gmail.com \
    --cc=horms@kernel.org \
    --cc=kabel@kernel.org \
    --cc=kory.maincent@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mwojtas@chromium.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicveronese@gmail.com \
    --cc=o.rempel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=romain.gantois@bootlin.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