* [PATCH v2 04/11] net: phy: Allow compile test of GPIO consumers if !GPIOLIB
[not found] <1438506475-31012-1-git-send-email-geert@linux-m68k.org>
@ 2015-08-02 9:09 ` Geert Uytterhoeven
2015-08-02 9:09 ` [PATCH v2 11/11] net: rfkill: " Geert Uytterhoeven
1 sibling, 0 replies; 3+ messages in thread
From: Geert Uytterhoeven @ 2015-08-02 9:09 UTC (permalink / raw)
To: Florian Fainelli
Cc: netdev, Linus Walleij, Alexandre Courbot, linux-gpio,
Geert Uytterhoeven
The GPIO subsystem provides dummy GPIO consumer functions if GPIOLIB is
not enabled. Hence drivers that depend on GPIOLIB, but use GPIO consumer
functionality only, can still be compiled if GPIOLIB is not enabled.
Relax the dependency on GPIOLIB if COMPILE_TEST is enabled, where
appropriate.
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
---
v2:
- Add Acked-by.
---
drivers/net/phy/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/phy/Kconfig b/drivers/net/phy/Kconfig
index 8ef81914422049ff..b98b4a2b8922a912 100644
--- a/drivers/net/phy/Kconfig
+++ b/drivers/net/phy/Kconfig
@@ -142,7 +142,8 @@ config MDIO_BITBANG
config MDIO_GPIO
tristate "Support for GPIO lib-based bitbanged MDIO buses"
- depends on MDIO_BITBANG && GPIOLIB
+ depends on MDIO_BITBANG
+ depends on GPIOLIB || COMPILE_TEST
---help---
Supports GPIO lib-based MDIO busses.
--
1.9.1
^ permalink raw reply related [flat|nested] 3+ messages in thread* [PATCH v2 11/11] net: rfkill: Allow compile test of GPIO consumers if !GPIOLIB
[not found] <1438506475-31012-1-git-send-email-geert@linux-m68k.org>
2015-08-02 9:09 ` [PATCH v2 04/11] net: phy: Allow compile test of GPIO consumers if !GPIOLIB Geert Uytterhoeven
@ 2015-08-02 9:09 ` Geert Uytterhoeven
2015-08-13 8:49 ` Johannes Berg
1 sibling, 1 reply; 3+ messages in thread
From: Geert Uytterhoeven @ 2015-08-02 9:09 UTC (permalink / raw)
To: Johannes Berg, David S. Miller
Cc: netdev, Linus Walleij, Alexandre Courbot, linux-gpio,
Geert Uytterhoeven
The GPIO subsystem provides dummy GPIO consumer functions if GPIOLIB is
not enabled. Hence drivers that depend on GPIOLIB, but use GPIO consumer
functionality only, can still be compiled if GPIOLIB is not enabled.
Relax the dependency on GPIOLIB if COMPILE_TEST is enabled, where
appropriate.
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
---
v2:
- Add Acked-by.
---
net/rfkill/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/net/rfkill/Kconfig b/net/rfkill/Kconfig
index 4c10e7e6c9f6ae53..598d374f6a35f714 100644
--- a/net/rfkill/Kconfig
+++ b/net/rfkill/Kconfig
@@ -36,7 +36,8 @@ config RFKILL_REGULATOR
config RFKILL_GPIO
tristate "GPIO RFKILL driver"
- depends on RFKILL && GPIOLIB
+ depends on RFKILL
+ depends on GPIOLIB || COMPILE_TEST
default n
help
If you say yes here you get support of a generic gpio RFKILL
--
1.9.1
^ permalink raw reply related [flat|nested] 3+ messages in thread