[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1j3irX-0006JO-FW@rmk-PC.armlinux.org.uk>
Date: Mon, 17 Feb 2020 16:03:11 +0000
From: Russell King <rmk+kernel@...linux.org.uk>
To: Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
Heiner Kallweit <hkallweit1@...il.com>
Cc: "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org
Subject: [PATCH net-next] net: phy: allow bcm84881 to be a module
Now that the phylib module loading issue has been resolved, we can
allow this PHY driver to be built as a module.
Signed-off-by: Russell King <rmk+kernel@...linux.org.uk>
---
This is a result of:
7d49a32a66d2 ("net: phy: ensure that phy IDs are correctly typed")
d2ed49cf6c13 ("mod_devicetable: fix PHY module format")
merged during the last cycle. Given that the bcm84881 driver is so
new, I'm not sure whether it's really important enough for -rc and
backporting to 5.5-stable or just queue it in net-next. My feeling
is that it's fairly low priority, and not important enough to
justify backporting to 5.5-stable unless someone really wants this
PHY driver to be modular. Therefore, I'm opting for net-next for
this posting.
drivers/net/phy/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/phy/Kconfig b/drivers/net/phy/Kconfig
index 9dabe03a668c..edb1cb8a228e 100644
--- a/drivers/net/phy/Kconfig
+++ b/drivers/net/phy/Kconfig
@@ -326,8 +326,8 @@ config BROADCOM_PHY
BCM5481, BCM54810 and BCM5482 PHYs.
config BCM84881_PHY
- bool "Broadcom BCM84881 PHY"
- depends on PHYLIB=y
+ tristate "Broadcom BCM84881 PHY"
+ depends on PHYLIB
---help---
Support the Broadcom BCM84881 PHY.
--
2.20.1
Powered by blists - more mailing lists