From: Matthew Wilcox <matthew@wil.cx>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: "'Jes Sorensen'" <jes@sgi.com>,
Alex Williamson <alex.williamson@hp.com>,
"Luck, Tony" <tony.luck@intel.com>, Adrian Bunk <bunk@stusta.de>,
Keith Owens <kaos@sgi.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] let IA64_GENERIC select more stuff
Date: Wed, 8 Feb 2006 14:24:16 -0700 [thread overview]
Message-ID: <20060208212416.GA1593@parisc-linux.org> (raw)
In-Reply-To: <200602081955.k18Jtug12275@unix-os.sc.intel.com>
On Wed, Feb 08, 2006 at 11:55:58AM -0800, Chen, Kenneth W wrote:
> CONFIG_IA64_GENERIC select CONFIG_ACPI, and CONFIG_ACPI select CONFIG_PCI,
> This whole thread is silly since the beginning and it is a moot point for
> all of previous discussions. What are we talking about exactly??
I think the problem is that ia64 is abusing the 'select' feature.
Select is a reverse dependency. It should be used to turn things on
which are required for this option to work. Right now, the generic
config uses it to turn on things which people think you probably want
if you're building a generic kernel.
IMO, the select statements should be deleted. They make it impossible to
build a generic kernel without ACPI or NUMA. While both are ubiquitous
in ia64 implementations, they really aren't mandatory.
next prev parent reply other threads:[~2006-02-08 21:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 18:35 [2.6 patch] let IA64_GENERIC select more stuff Luck, Tony
2006-02-08 19:21 ` Alex Williamson
2006-02-08 19:24 ` Jes Sorensen
2006-02-08 19:55 ` Chen, Kenneth W
2006-02-08 21:24 ` Matthew Wilcox [this message]
2006-02-08 21:36 ` Chen, Kenneth W
-- strict thread matches above, loose matches on Subject: below --
2006-02-08 22:35 Luck, Tony
2006-02-08 19:48 Luck, Tony
2006-02-07 22:11 [2.6 patch] IA64_GENERIC shouldn't select other stuff Adrian Bunk
2006-02-07 22:37 ` Keith Owens
2006-02-07 23:17 ` [2.6 patch] let IA64_GENERIC select more stuff Adrian Bunk
2006-02-08 0:52 ` Chen, Kenneth W
2006-02-08 1:19 ` Adrian Bunk
2006-02-08 1:40 ` Chen, Kenneth W
2006-02-08 2:08 ` Adrian Bunk
2006-02-08 2:17 ` Chen, Kenneth W
2006-02-08 2:43 ` Adrian Bunk
2006-02-08 2:48 ` Keith Owens
2006-02-08 2:54 ` Matthew Wilcox
2006-02-08 2:58 ` Chen, Kenneth W
2006-02-08 3:51 ` Adrian Bunk
2006-02-08 5:52 ` Chen, Kenneth W
2006-02-08 11:59 ` Adrian Bunk
2006-02-08 13:38 ` Jes Sorensen
2006-02-08 21:38 ` Adrian Bunk
2006-02-08 22:24 ` Chen, Kenneth W
2006-02-08 22:49 ` Adrian Bunk
2006-02-09 12:53 ` Jes Sorensen
2006-02-09 13:18 ` Matthew Wilcox
2006-02-09 13:26 ` Jes Sorensen
2006-02-09 14:16 ` Adrian Bunk
2006-02-09 15:19 ` Jes Sorensen
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=20060208212416.GA1593@parisc-linux.org \
--to=matthew@wil.cx \
--cc=alex.williamson@hp.com \
--cc=bunk@stusta.de \
--cc=jes@sgi.com \
--cc=kaos@sgi.com \
--cc=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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