From 08ed044595b404fa626f71c9b1c1fbc599ad7587 Mon Sep 17 00:00:00 2001 From: Gabor Juhos Date: Sat, 12 May 2012 12:05:19 +0000 Subject: linux/2.6.37: R.I.P. SVN-Revision: 31687 --- .../generic/patches-2.6.37/832-ledtrig_usbdev.patch | 21 --------------------- 1 file changed, 21 deletions(-) delete mode 100644 target/linux/generic/patches-2.6.37/832-ledtrig_usbdev.patch (limited to 'target/linux/generic/patches-2.6.37/832-ledtrig_usbdev.patch') diff --git a/target/linux/generic/patches-2.6.37/832-ledtrig_usbdev.patch b/target/linux/generic/patches-2.6.37/832-ledtrig_usbdev.patch deleted file mode 100644 index 25c6745..0000000 --- a/target/linux/generic/patches-2.6.37/832-ledtrig_usbdev.patch +++ /dev/null @@ -1,21 +0,0 @@ ---- a/drivers/leds/Kconfig -+++ b/drivers/leds/Kconfig -@@ -450,4 +450,11 @@ config LEDS_TRIGGER_NETDEV - This allows LEDs to be controlled by network device activity. - If unsure, say Y. - -+config LEDS_TRIGGER_USBDEV -+ tristate "LED USB device Trigger" -+ depends on USB && LEDS_TRIGGERS -+ help -+ This allows LEDs to be controlled by the presence/activity of -+ an USB device. If unsure, say N. -+ - endif # NEW_LEDS ---- a/drivers/leds/Makefile -+++ b/drivers/leds/Makefile -@@ -54,3 +54,4 @@ obj-$(CONFIG_LEDS_TRIGGER_GPIO) += ledt - 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_USBDEV) += ledtrig-usbdev.o -- cgit v1.1