From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: Len Brown <lenb@kernel.org>
Cc: Andreas Herrmann <andreas.herrmann3@amd.com>,
Steven Whitehouse <swhiteho@redhat.com>, Andi Kleen <ak@suse.de>,
Shai Fultheim <shai@scalex86.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 7/12] acpi: fix another compile warning
Date: Wed, 20 Jun 2007 11:25:48 -0700 [thread overview]
Message-ID: <20070620182548.GA561@localdomain> (raw)
In-Reply-To: <200706200936.31236.lenb@kernel.org>
On Wed, Jun 20, 2007 at 09:36:30AM -0400, Len Brown wrote:
> On Wednesday 20 June 2007 04:49, Andreas Herrmann wrote:
> > On Tue, Jun 19, 2007 at 11:38:02PM -0400, Len Brown wrote:
> > > On Tuesday 19 June 2007 18:50, Andreas Herrmann wrote:
>
> I fear, however, that this patch defeats the purpose of
> b0bd35e622ffbda2c01dc67a0381c6a18817a29a -- which was to make selecting
> NUMA more user-friendly. So it might make more sense to simply revert that
> patch entirely.
>
> The underlying problem is that Kconfig doesn't support using select
> on targets which themselves have dependencies.
>
> Signed-off-by: Len Brown <len.brown@intel.com>
>
>
> diff --git a/arch/x86_64/Kconfig b/arch/x86_64/Kconfig
> index 5ce9443..e9d7767 100644
> --- a/arch/x86_64/Kconfig
> +++ b/arch/x86_64/Kconfig
> @@ -364,9 +364,9 @@ config NODES_SHIFT
> config X86_64_ACPI_NUMA
> bool "ACPI NUMA detection"
> depends on NUMA
> - select ACPI
> + depends on ACPI
> select PCI
> - select ACPI_NUMA
> + depends on ACPI_NUMA
> default y
> help
> Enable ACPI SRAT based node topology detection.
> -
arch/x86_64/Kconfig:706:error: found recursive dependency: PCI -> ACPI ->
X86_64_ACPI_NUMA -> PCI
-> USB_ARCH_HAS_OHCI -> USB_ARCH_HAS_HCD -> MOUSE_APPLETOUCH -> USB ->
USB_SISUSBVGAmake[1]: *** [menuconfig] Error 1
I guess we have to change PCI to 'depends on' as well.
Else, select PM?
I am OK with either approach.
Thanks,
Kiran
Paper over 'select' inadequacies.
Signed-off-by: Ravikiran Thirumalai <kiran@scalex86.org>
Index: linux-2.6.22-rc5/arch/x86_64/Kconfig
===================================================================
--- linux-2.6.22-rc5.orig/arch/x86_64/Kconfig 2007-06-18 16:02:19.571323415 -0700
+++ linux-2.6.22-rc5/arch/x86_64/Kconfig 2007-06-20 11:34:29.845354250 -0700
@@ -366,6 +366,7 @@ config X86_64_ACPI_NUMA
depends on NUMA
select ACPI
select PCI
+ select PM
select ACPI_NUMA
default y
help
next prev parent reply other threads:[~2007-06-20 18:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 22:50 [PATCH 7/12] acpi: fix another compile warning Andreas Herrmann
2007-06-20 3:38 ` Len Brown
2007-06-20 3:49 ` Randy Dunlap
2007-06-20 3:51 ` Randy Dunlap
2007-06-20 4:41 ` Len Brown
2007-06-20 9:31 ` Andreas Herrmann
2007-06-20 14:28 ` Randy Dunlap
2007-06-20 8:49 ` Andreas Herrmann
2007-06-20 13:36 ` Len Brown
2007-06-20 13:46 ` Andi Kleen
2007-06-20 18:25 ` Ravikiran G Thirumalai [this message]
2007-06-21 18:36 ` Andreas Herrmann
2007-06-22 14:39 ` Andreas Herrmann
2007-06-23 3:55 ` Andrew Morton
2007-06-23 4:28 ` 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=20070620182548.GA561@localdomain \
--to=kiran@scalex86.org \
--cc=ak@suse.de \
--cc=andreas.herrmann3@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shai@scalex86.org \
--cc=swhiteho@redhat.com \
/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