From: "James C. Georgas" <jgeorgas@georgas.ca>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: broken ACPI NUMA config option
Date: Sat, 08 Sep 2007 21:22:41 -0400 [thread overview]
Message-ID: <1189300961.13467.47.camel@Tachyon.home> (raw)
In-Reply-To: <20070908180904.656f3d03.randy.dunlap@oracle.com>
On Sat, 2007-08-09 at 18:09 -0700, Randy Dunlap wrote:
> On Sat, 08 Sep 2007 18:51:39 -0400 James C. Georgas wrote:
>
> > If I select X86_64_ACPI_NUMA, then ACPI_NUMA is (properly) selected
> > automatically, but ACPI is not selected automatically. This causes
> > ACPI_NUMA to not be built, and the kernel compile fails with unresolved
> > symbols.
>
> exactly what kernel version??
>
>
It's 2.6.22.6. I'm thinking a fix would be to add "select PM" to
X86_64_ACPI_NUMA.
I'm also thinking that maybe K8_NUMA should be changed from "depends on
PCI" to "select PCI", like X86_64_ACPI_NUMA is. That would fix the
pseudo dependency they have between them (i.e. selecting
X86_64_ACPI_NUMA causes PCI to be selected, which then makes K8_NUMA
visible, because its PCI dependency is now satisfied).
James
/\V
next prev parent reply other threads:[~2007-09-09 1:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 22:51 James C. Georgas
2007-09-08 22:54 ` James C. Georgas
2007-09-08 23:33 ` James C. Georgas
2007-09-09 1:09 ` Randy Dunlap
2007-09-09 1:16 ` Randy Dunlap
2007-09-09 3:48 ` James C. Georgas
2007-09-09 4:24 ` Yinghai Lu
2007-09-09 5:00 ` Randy Dunlap
2007-09-09 13:41 ` James C. Georgas
2007-09-09 17:32 ` Randy Dunlap
2007-09-09 1:22 ` James C. Georgas [this message]
2007-09-09 9:07 ` Andi Kleen
2007-09-09 13:19 ` [PATCH] KCONFIG: fix pseudo dependency between K8_NUMA and X86_64_ACPI_NUMA config options James C. Georgas
2007-09-09 13:46 ` Andi Kleen
2007-09-09 18:43 ` James C. Georgas
2007-09-09 2:36 broken ACPI NUMA config option James C. Georgas
2007-09-09 7:06 ` Sam Ravnborg
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=1189300961.13467.47.camel@Tachyon.home \
--to=jgeorgas@georgas.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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
all inboxes | Powered by JetHome®