diff options
author | David S. Miller <davem@davemloft.net> | 2008-04-23 12:33:32 +0200 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2008-04-23 12:33:32 +0200 |
commit | 00713e224e718b350cb0148184dc7884885d00b9 (patch) | |
tree | da7c72704aa8e099343dd16f9fbf0519e1e41ecb /drivers/leds | |
parent | [IPSEC]: Fix catch-22 with algorithm IDs above 31 (diff) | |
download | linux-00713e224e718b350cb0148184dc7884885d00b9.tar.xz linux-00713e224e718b350cb0148184dc7884885d00b9.zip |
leds: Do not guard NEW_LEDS with HAS_IOMEM
The LEDS infrastructure itself does not require anything
that a platform dependant upon HAS_IOMEM.
The individual drivers do, but they are properly guarded
with the necessary platform dependencies.
One can even imagine a hypervisor based LED driver that
a platform without HAS_IOMEM might have.
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/leds')
-rw-r--r-- | drivers/leds/Kconfig | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig index 859814f62cb0..91d36d07e6ae 100644 --- a/drivers/leds/Kconfig +++ b/drivers/leds/Kconfig @@ -1,6 +1,5 @@ menuconfig NEW_LEDS bool "LED Support" - depends on HAS_IOMEM help Say Y to enable Linux LED support. This allows control of supported LEDs from both userspace and optionally, by kernel events (triggers). |