[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zb52rPnYmkmqTTr4@shell.armlinux.org.uk>
Date: Sat, 3 Feb 2024 17:23:56 +0000
From: "Russell King (Oracle)" <linux@...linux.org.uk>
To: Andrew Lunn <andrew@...n.ch>
Cc: Heiner Kallweit <hkallweit1@...il.com>,
Christian Marangi <ansuelsmth@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Michal Simek <michal.simek@....com>, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH net-next] net: phy: constify phydev->drv
On Sat, Feb 03, 2024 at 05:56:19PM +0100, Andrew Lunn wrote:
> On Fri, Feb 02, 2024 at 05:41:45PM +0000, Russell King (Oracle) wrote:
> > Device driver structures are shared between all devices that they
> > match, and thus nothing should never write to the device driver
>
> nothing should never ???
>
> I guess the never should be ever?
Yes, thanks for spotting that.
> > struct gmii2rgmii {
> > struct phy_device *phy_dev;
> > - struct phy_driver *phy_drv;
> > + const struct phy_driver *phy_drv;
> > struct phy_driver conv_phy_drv;
> > struct mdio_device *mdio;
> > };
>
> Did you build testing include xilinx_gmii2rgmii.c ? It does funky
> things with phy_driver structures.
CONFIG_XILINX_GMII2RGMII=m
So yes.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
Powered by blists - more mailing lists