public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: Matthew Garrett <mjg@redhat.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: Fix recursive Kconfig dependency
Date: Wed, 15 Dec 2010 21:35:35 +0100	[thread overview]
Message-ID: <201012152135.35941.PeterHuewe@gmx.de> (raw)
In-Reply-To: <1291850970-7190-1-git-send-email-peterhuewe@gmx.de>

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@gmx.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 ?

  reply	other threads:[~2010-12-15 20:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 23:29 [PATCH] platform/x86: Fix recursive Kconfig dependency Peter Huewe
2010-12-15 20:35 ` Peter Hüwe [this message]
2010-12-15 20:49   ` Corentin Chary
2010-12-15 20:51     ` Randy Dunlap
2010-12-15 21:14       ` Peter Hüwe
2010-12-17 11:30         ` Sedat Dilek
2010-12-19 19:00           ` Peter Hüwe
2010-12-20 14:46             ` Sedat Dilek
2010-12-20 17:09               ` Peter Hüwe
2010-12-20 17:24                 ` Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201012152135.35941.PeterHuewe@gmx.de \
    --to=peterhuewe@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox