path: root/drivers/net/phy/phy_device.c
diff options
authorKrzysztof Halasa <khc@pm.waw.pl>2008-12-25 16:50:41 -0800
committerDavid S. Miller <davem@davemloft.net>2008-12-25 16:50:41 -0800
commit161c8d2f50109b44b664eaf23831ea1587979a61 (patch)
tree1d9b2b4aaa72296f98c449e6f955ade61e84ed02 /drivers/net/phy/phy_device.c
parentf7d1b9f5aafa371d7f51f644aa3c38bc914e9205 (diff)
net: PHYLIB mdio fixes #2
The PHYLIB mdio code has more problems in error paths: - mdiobus_release can be called before bus->state is set to MDIOBUS_REGISTERED - mdiobus_scan allocates resources which need to be freed - the comment is wrong, the resistors used are actually pull-ups. Signed-off-by: Krzysztof Halasa <khc@pm.waw.pl> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/phy/phy_device.c')
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
index f84f6a1b530..e35460165bf 100644
--- a/drivers/net/phy/phy_device.c
+++ b/drivers/net/phy/phy_device.c
@@ -232,7 +232,7 @@ struct phy_device * get_phy_device(struct mii_bus *bus, int addr)
return NULL;
- * Broken hardware is sometimes missing the pull down resistor on the
+ * Broken hardware is sometimes missing the pull-up resistor on the
* MDIO line, which results in reads to non-existent devices returning
* 0 rather than 0xffff. Catch this here and treat 0 as a non-existent
* device as well.