linux-kernel - CONFIG_BACKLIGHT_CLASS_DEVICE and unmet direct dependencies

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <4D5E2302.4010204@gmail.com>
Date:	Fri, 18 Feb 2011 08:42:58 +0100
From:	René Herman <rene.herman@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: CONFIG_BACKLIGHT_CLASS_DEVICE and unmet direct dependencies

Good day.

*config is barfing:

===
warning: (STUB_POULSBO && HAS_IOMEM && PCI && ACPI || FB_BACKLIGHT && 
HAS_IOMEM && FB || DRM_I915 && <choice> && AGP_INTEL && ACPI || 
PANEL_SHARP_LS037V7DW01 && HAS_IOMEM && OMAP2_DSS || PANEL_ACX565AKM && 
HAS_IOMEM && OMAP2_DSS && OMAP2_DSS_SDI && SPI || USB_APPLEDISPLAY && 
USB_SUPPORT && USB || ASUS_LAPTOP && X86 && X86_PLATFORM_DEVICES && ACPI 
&& !ACPI_ASUS && INPUT && (RFKILL || RFKILL=n) || SONY_LAPTOP && X86 && 
X86_PLATFORM_DEVICES && ACPI && INPUT && RFKILL || THINKPAD_ACPI && X86 
&& X86_PLATFORM_DEVICES && ACPI && INPUT && (RFKILL || RFKILL=n) || 
EEEPC_LAPTOP && X86 && X86_PLATFORM_DEVICES && ACPI && INPUT && 
EXPERIMENTAL && (RFKILL || RFKILL=n) && HOTPLUG_PCI || ACPI_ASUS && X86 
&& X86_PLATFORM_DEVICES && ACPI || ACPI_CMPC && X86_PLATFORM_DEVICES && 
X86 && ACPI && (RFKILL || RFKILL=n)) selects BACKLIGHT_CLASS_DEVICE 
which has unmet direct dependencies (HAS_IOMEM && BACKLIGHT_LCD_SUPPORT)
===

at me -- twice per invocation. Is this a local config problem or should 
some of these selections be adjusted?

Rene.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/