| Message ID | 20081117140313.8019.48296.stgit@Programuotojas.82-135-208-232.ip.zebra.lt |
|---|---|
| State | Accepted, archived |
| Delegated to: | David Miller |
| Headers | show |
From: Paulius Zaleckas <paulius.zaleckas@teltonika.lt> Date: Mon, 17 Nov 2008 16:03:13 +0200 > All MDIO bus drivers currently name bus with "%x" format. > There is one exception where mv643xx_eth driver is using "%d". > Phy address on the bus uses format "%02x". > > Fixing phy name example to match all real life MDIO drivers. > > Signed-off-by: Paulius Zaleckas <paulius.zaleckas@teltonika.lt> Applied, thanks! -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/networking/phy.txt b/Documentation/networking/phy.txt index 8df6a7b..88bb71b 100644 --- a/Documentation/networking/phy.txt +++ b/Documentation/networking/phy.txt @@ -96,7 +96,7 @@ Letting the PHY Abstraction Layer do Everything static void adjust_link(struct net_device *dev); Next, you need to know the device name of the PHY connected to this device. - The name will look something like, "phy0:0", where the first number is the + The name will look something like, "0:00", where the first number is the bus id, and the second is the PHY's address on that bus. Typically, the bus is responsible for making its ID unique.
All MDIO bus drivers currently name bus with "%x" format. There is one exception where mv643xx_eth driver is using "%d". Phy address on the bus uses format "%02x". Fixing phy name example to match all real life MDIO drivers. Signed-off-by: Paulius Zaleckas <paulius.zaleckas@teltonika.lt> --- Documentation/networking/phy.txt | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html