[PATCH net-next 5/9] phy: add phy_get_rx_polarity() and phy_get_tx_polarity()

Vladimir Oltean vladimir.oltean at nxp.com
Tue Nov 25 09:02:57 PST 2025


On Mon, Nov 24, 2025 at 08:01:21PM -0800, Jakub Kicinski wrote:
> > The proposed maintainership model is joint custody between netdev and
> > linux-phy, because of the fact that these properties can be applied to
> > Ethernet PCS blocks just as well as Generic PHY devices. I've added as
> > maintainers those from "ETHERNET PHY LIBRARY", "NETWORKING DRIVERS" and
> > "GENERIC PHY FRAMEWORK".
> 
> I dunno.. ain't no such thing as "joint custody" maintainership.
> We have to pick one tree. Given the set of Ms here, I suspect 
> the best course of action may be to bubble this up to its own tree.
> Ask Konstantin for a tree in k.org, then you can "co-post" the patches
> for review + PR link in the cover letter (e.g. how Tony from Intel
> submits their patches). This way not networking and PHY can pull
> the shared changes with stable commit IDs.

I can see how this makes some sense. If nobody has any objection, I'll
follow up to this by emailing Konstantin about a git tree for shared
infrastructure between generic PHY and networking.

> We can do out-of-sequence netdev call tomorrow if folks want to talk
> this thru (8:30am Pacific)

Not sure it's that big of a discussion topic.

> > +GENERIC PHY COMMON PROPERTIES
> > +M:	Andrew Lunn <andrew at lunn.ch>
> > +M:	"David S. Miller" <davem at davemloft.net>
> > +M:	Eric Dumazet <edumazet at google.com>
> > +M:	Heiner Kallweit <hkallweit1 at gmail.com>
> > +M:	Jakub Kicinski <kuba at kernel.org>
> > +M:	Kishon Vijay Abraham I <kishon at kernel.org>
> > +M:	Paolo Abeni <pabeni at redhat.com>
> > +R:	Russell King <linux at armlinux.org.uk>
> > +M:	Vinod Koul <vkoul at kernel.org>
> 
> checkpatch nit: apparently it wants all Ms first, then all Rs.

Thanks for pointing this out.

This will probably have to be changed quite a bit in v2 if the "separate
git tree" idea is going to be implemented. I'll probably start with an
empty list and request volunteers to step up.



More information about the linux-arm-kernel mailing list