From: Jakub Kicinski <kuba@kernel.org>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
thomas.petazzoni@bootlin.com, "Andrew Lunn" <andrew@lunn.ch>,
"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>,
"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, "Antoine Tenart" <atenart@kernel.org>,
devicetree@vger.kernel.org, "Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Romain Gantois" <romain.gantois@bootlin.com>,
"Daniel Golle" <daniel@makrotopia.org>,
"Dimitri Fedrau" <dimitri.fedrau@liebherr.com>,
"Tariq Toukan" <tariqt@nvidia.com>
Subject: Re: [PATCH net-next v19 00/15] net: phy: Introduce PHY ports representation
Date: Wed, 26 Nov 2025 19:00:35 -0800 [thread overview]
Message-ID: <20251126190035.2a4e0558@kernel.org> (raw)
In-Reply-To: <20251122124317.92346-1-maxime.chevallier@bootlin.com>
On Sat, 22 Nov 2025 13:42:59 +0100 Maxime Chevallier wrote:
> This is v19 of the phy_port work. Patches 2 and 3 lack PHY maintainers reviews.
>
> This v19 has no changes compared to v18, but patch 2 was rebased on top
> of the recent 1.6T linkmodes.
>
> Thanks for everyone's patience and reviews on that work ! Now, the
> usual blurb for the series description.
Hopefully we can still make v6.19, but we hooked up Claude Code review
to patchwork this week, and it points out some legit issues here :(
Some look transient but others are definitely legit, please look thru
this:
https://netdev-ai.bots.linux.dev/ai-review.html?id=5388d317-98c9-458e-8655-d60f31112574
--
pw-bot: cr
next prev parent reply other threads:[~2025-11-27 3:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-22 12:42 [PATCH net-next v19 00/15] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 01/15] dt-bindings: net: Introduce the ethernet-connector description Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 02/15] net: ethtool: Introduce ETHTOOL_LINK_MEDIUM_* values Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 03/15] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 04/15] net: phy: dp83822: Add support for phy_port representation Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 05/15] dt-bindings: net: dp83822: Deprecate ti,fiber-mode Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 06/15] net: phy: Create a phy_port for PHY-driven SFPs Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 07/15] net: phy: Introduce generic SFP handling for PHY drivers Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 08/15] net: phy: marvell-88x2222: Support SFP through phy_port interface Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 09/15] net: phy: marvell: " Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 10/15] net: phy: marvell10g: Support SFP through phy_port Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 11/15] net: phy: at803x: Support SFP through phy_port interface Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 12/15] net: phy: qca807x: " Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 13/15] net: phy: Only rely on phy_port for PHY-driven SFP Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 14/15] net: phy: dp83822: Add SFP support through the phy_port interface Maxime Chevallier
2025-11-22 12:43 ` [PATCH net-next v19 15/15] Documentation: networking: Document the phy_port infrastructure Maxime Chevallier
2025-11-27 3:00 ` Jakub Kicinski [this message]
2025-11-27 8:43 ` [PATCH net-next v19 00/15] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-11-27 15:14 ` Andrew Lunn
2025-11-27 10:10 ` Maxime Chevallier
2025-11-27 12:46 ` Paolo Abeni
2025-11-27 15:53 ` Maxime Chevallier
2025-11-27 16:03 ` Andrew Lunn
2025-11-28 12:56 ` Chris Mason
2025-11-28 13:06 ` Chris Mason
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=20251126190035.2a4e0558@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--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=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--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=robh@kernel.org \
--cc=romain.gantois@bootlin.com \
--cc=tariqt@nvidia.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).