[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7f4f7fc2-6bf3-4ecb-9c13-763e2d4f176f@lunn.ch>
Date: Sat, 3 Feb 2024 17:56:19 +0100
From: Andrew Lunn <andrew@...n.ch>
To: "Russell King (Oracle)" <rmk+kernel@...linux.org.uk>
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 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?
> diff --git a/drivers/net/phy/xilinx_gmii2rgmii.c b/drivers/net/phy/xilinx_gmii2rgmii.c
> index 7fd9fe6a602b..7b1bc5fcef9b 100644
> --- a/drivers/net/phy/xilinx_gmii2rgmii.c
> +++ b/drivers/net/phy/xilinx_gmii2rgmii.c
> @@ -22,7 +22,7 @@
>
> 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.
Thanks
Andrew
Powered by blists - more mailing lists