summaryrefslogtreecommitdiffstats
path: root/Makefile
diff options
context:
space:
mode:
authorSascha Hauer <s.hauer@pengutronix.de>2015-05-04 08:16:20 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2015-05-05 13:53:15 +0200
commitc05380f61e1edf4d8eb5b8a60c0d85b451c4fd13 (patch)
treedb3a1ecaf2567ed7f1c72569716c6e21ed6a27be /Makefile
parentcbc24926213be28321fc129bdb8226d1588a3918 (diff)
downloadbarebox-c05380f61e1edf4d8eb5b8a60c0d85b451c4fd13.tar.gz
barebox-c05380f61e1edf4d8eb5b8a60c0d85b451c4fd13.tar.xz
net: phy: Do not double remove phy device
This fixes: 80264a8 driver: Call bus->remove instead of driver->remove On mvebu it happens that: Upon device shutdown, when iterating through the active device list, the phy0 device is removed before mdio-mvebu. Then, when the mdio bus device is removed, the phy0 device is removed again, here: mdio_bus_remove(on mdio-mvebu) mvebu_mdio_remove mdiobus_unregister unregister_device mdio_bus_remove(on phy0) Fix this by setting the mdio busses phy_map[phy->addr] to NULL when unregistering the phy device, so that mdiobus_unregister no longer finds a valid phy_device when iterating over the busses device list. Reported-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Tested-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions