linux-kernel - Re: [PATCH] platform/x86: Fix recursive Kconfig dependency

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <201012152135.35941.PeterHuewe@gmx.de>
Date:	Wed, 15 Dec 2010 21:35:35 +0100
From:	Peter Hüwe <PeterHuewe@....de>
To:	Matthew Garrett <mjg@...hat.com>
Cc:	platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] platform/x86: Fix recursive Kconfig dependency

Am Donnerstag 09 Dezember 2010, 00:29:30 schrieb Peter Huewe:
> This patch removes a recursive dependency which causes a build failure
> [1-3] by changing the ASUS_WMI from select ACPI_WMI to depend on
> ACPI_WMI as most other _WMI config options do.
> 
> Signed-off-by: Peter Huewe <peterhuewe@....de>
> ---
> Error Message:
> 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
> 
> 
> References:
> [1] http://kisskb.ellerman.id.au/kisskb/buildresult/3607123/
> [2] http://kisskb.ellerman.id.au/kisskb/buildresult/3607218/
> [3] http://kisskb.ellerman.id.au/kisskb/buildresult/3607139/
> 
> KernelVersion: linux-next-20101208
> 


Ping - Any updates yet ?
--
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/