From: Keith Owens <kaos@ocs.com.au>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: i386 Kconfig options out of order
Date: Tue, 23 May 2006 22:51:13 +1000 [thread overview]
Message-ID: <8522.1148388673@ocs3> (raw)
In-Reply-To: Your message of "Tue, 23 May 2006 11:30:39 +0200." <Pine.LNX.4.64.0605231127550.17704@scrub.home>
Roman Zippel (on Tue, 23 May 2006 11:30:39 +0200 (CEST)) wrote:
>Hi,
>
>On Tue, 23 May 2006, Keith Owens wrote:
>
>> Options NUMA and EFI in arch/i386/Kconfig depend on ACPI but they
>> appear before the ACPI option. make oldconfig with no initial setting
>> for CONFIG_ACPI will prompt for these options, but if you then say No
>> to CONFIG_ACPI the options will silently be turned off.
>
>That's the normal behaviour.
Fair enough. I was switching between configs with ACPI=y and ACPI=n,
every time I editted .config to remove the current ACPI setting and ran
oldconfig to insert the new setting, I got prompted for these extra
options. Forward dependencies in configs, yuck.
prev parent reply other threads:[~2006-05-23 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 6:10 i386 Kconfig options out of order Keith Owens
2006-05-23 9:30 ` Roman Zippel
2006-05-23 12:51 ` Keith Owens [this message]
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=8522.1148388673@ocs3 \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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