Using CONFIG_MODVERSIONS is a bad idea, disable it and no longer mark brcm63xx as...

[openwrt.git] / target / linux / adm5120 / patches-2.6.26 / 009-adm5120_leds_switch_trigger.patch

diff --git a/target/linux/adm5120/patches-2.6.26/009-adm5120_leds_switch_trigger.patch b/target/linux/adm5120/patches-2.6.26/009-adm5120_leds_switch_trigger.patch
index 341d802..a0d363a 100644 (file)
--- a/target/linux/adm5120/patches-2.6.26/009-adm5120_leds_switch_trigger.patch
+++ b/target/linux/adm5120/patches-2.6.26/009-adm5120_leds_switch_trigger.patch
@@ -1,12 +1,12 @@
 --- a/drivers/leds/Kconfig
 +++ b/drivers/leds/Kconfig
-@@ -215,4 +215,12 @@
-       tristate "LED Morse Trigger"
-       depends on LEDS_TRIGGERS
+@@ -207,4 +207,12 @@
+         This allows LEDs to be controlled by network device activity.
+         If unsure, say Y.
  
 +config LEDS_TRIGGER_ADM5120_SWITCH
 +      tristate "LED ADM5120 Switch Port Status Trigger"
-+      depends on LEDS_TRIGGERS && LEDS_ADM5120
++      depends on LEDS_TRIGGERS && ADM5120
 +      help
 +        This allows LEDs to be controlled by the port states of
 +        the ADM5120 built-in Ethernet Switch
@@ -16,7 +16,7 @@
 --- a/drivers/leds/Makefile
 +++ b/drivers/leds/Makefile
 @@ -30,3 +30,4 @@
- obj-$(CONFIG_LEDS_TRIGGER_HEARTBEAT)  += ledtrig-heartbeat.o
  obj-$(CONFIG_LEDS_TRIGGER_DEFAULT_ON) += ledtrig-default-on.o
  obj-$(CONFIG_LEDS_TRIGGER_MORSE)      += ledtrig-morse.o
+ obj-$(CONFIG_LEDS_TRIGGER_NETDEV)      += ledtrig-netdev.o
 +obj-$(CONFIG_LEDS_TRIGGER_ADM5120_SWITCH) += ledtrig-adm5120-switch.o