net: phy: microchip_t1: Don't set .config_aneg
PATCH 1/1 net: phy: microchip_t1: Don't set .config_aneg
The .config_aneg in microchip_t1 is genphy_config_aneg, so it's not needed, because the phy core will call genphy_config_aneg() if the .config_aneg is NULL.
Signed-off-by Jisheng Zhang <[email protected]>
--- drivers/net/phy/microchip_t1.c | 1 - 1 file changed, 1 deletion(-)
drivers/net/phy/microchip_t1.c +0 -1
@@ -219,7 +219,6 @@ static struct phy_driver microchip_t1_phy_driver[] = { .features = PHY_BASIC_T1_FEATURES, .config_init = lan87xx_config_init, - .config_aneg = genphy_config_aneg, .ack_interrupt = lan87xx_phy_ack_interrupt, .config_intr = lan87xx_phy_config_intr,
Signature · 1 line
2.29.2
Quoted 5 lines · Jisheng Zhang
The .config_aneg in
microchip_t1isgenphy_config_aneg, so it's not needed, because the phy core will callgenphy_config_aneg()if the .config_aneg is NULL.Signed-off-by Jisheng Zhang <[email protected]>
Reviewed-by Andrew Lunn <[email protected]>
Andrew
Quoted 8 lines · On Mon, 9 Nov 2020 18:36:22 +0100 Andrew Lunn wrote:
Quoted 5 lines · Jisheng Zhang
The .config_aneg in
microchip_t1isgenphy_config_aneg, so it's not needed, because the phy core will callgenphy_config_aneg()if the .config_aneg is NULL.Signed-off-by Jisheng Zhang <[email protected]>Reviewed-by Andrew Lunn <[email protected]>
Applied, thanks!