diff options
| author | Mark Brown <broonie@opensource.wolfsonmicro.com> | 2011-01-10 14:37:02 +0000 |
|---|---|---|
| committer | Matthew Garrett <mjg@redhat.com> | 2011-01-10 11:55:25 -0500 |
| commit | 0c51a4d8abd6ed5ba55f828840c6b78ab672644b (patch) | |
| tree | d2e147da632df6a00c17d3403c05b9f33a7b954d /COPYING | |
| parent | a46a780835f394869e1fbbef8b528a1e02193e78 (diff) | |
| download | linux-0c51a4d8abd6ed5ba55f828840c6b78ab672644b.tar.bz2 | |
platform/x86: Consistently select LEDS Kconfig options
Currently the x86 platform devices are not consistent about selecting
or depending on the LEDs Kconfig variables, and this inconsistency
leads to Kconfig getting upset and refusing to offer LEDs (even on
non-x86 platforms):
drivers/platform/x86/Kconfig:422:error: recursive dependency detected!
drivers/platform/x86/Kconfig:422: symbol EEEPC_WMI depends on ACPI_WMI
drivers/platform/x86/Kconfig:438: symbol ACPI_WMI is selected by ACER_WMI
drivers/platform/x86/Kconfig:18: symbol ACER_WMI depends on LEDS_CLASS
drivers/leds/Kconfig:10: symbol LEDS_CLASS is selected by EEEPC_WMI
Fix this by always selecting rather than depending on the symbols as
slightly more drivers use this approach already and it seems more
user friendly.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Matthew Garrett <mjg@redhat.com>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions