From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-acpi@intel.com,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: CONFIG_ACPI totally broken (2.6.9-rc1-mm2)
Date: Tue, 31 Aug 2004 12:41:51 -0700 [thread overview]
Message-ID: <235850000.1093981311@flay> (raw)
In-Reply-To: <20040831122756.675eaa86.akpm@osdl.org>
>> > OK, not only does it not compile in -mm2, you also can't disable it.
>>
>> The exact same config file works fine in -mm1 ... it's just the -mm2
>> one that's broken.
OK, removing all the "select ACPI" statements from arch/i386/Kconfig
fixes it ... but all of the things that those were under were already
disabled. So I think it might be a Kconfig bug.
ftp://ftp.kernel.org/pub/linux/kernel/people/mbligh/config/config.numaq
should demonstrate it well.
>> > Moreover, if you try you get this:
>> >
>> > scripts/kconfig/mconf arch/i386/Kconfig
>> > Warning! Found recursive dependency: ACPI PCI_MMCONFIG ACPI ACPI_AC
>> > Warning! Found recursive dependency: ACPI PCI_MMCONFIG ACPI ACPI_PROCESSOR X86_POWERNOW_K7_ACPI
>> > Warning! Found recursive dependency: ACPI PCI_MMCONFIG ACPI ACPI_PROCESSOR X86_POWERNOW_K8_ACPI
>> > Warning! Found recursive dependency: ACPI PCI_MMCONFIG ACPI ACPI_EC
>> > Warning! Found recursive dependency: ACPI PCI_MMCONFIG ACPI ACPI_PROCESSOR X86_SPEEDSTEP_CENTRINO_ACPI
>> > Warning! Found recursive dependency: DRM_I830 DRM_I915 DRM_I830
>
> Yeah, that one. I bugged Len the other day, but perhaps he's
> out of town or something.
Nah, he's talking to me on IRC, so he can't escape ;-)
next prev parent reply other threads:[~2004-09-01 0:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 19:08 CONFIG_ACPI totally broken (2.6.9-rc1-mm2) Martin J. Bligh
2004-08-31 19:13 ` Martin J. Bligh
2004-08-31 19:27 ` Andrew Morton
2004-08-31 19:41 ` Martin J. Bligh [this message]
2004-09-01 0:55 ` Roman Zippel
[not found] <566B962EB122634D86E6EE29E83DD808182C4C12@hdsmsx403.hd.intel.com>
2004-09-01 1:47 ` Len Brown
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=235850000.1093981311@flay \
--to=mbligh@aracnet.com \
--cc=akpm@osdl.org \
--cc=linux-acpi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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