From: Jes Sorensen <jes@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
bjorn_helgaas@hp.com, "Nick Piggin" <nickpiggin@yahoo.com.au>,
"Robin Holt" <holt@sgi.com>, "Dean Nelson" <dcn@sgi.com>,
"Hugh Dickins" <hugh@veritas.com>,
"Linus Torvalds" <torvalds@osdl.org>,
linux-ia64 <linux-ia64@vger.kernel.org>,
"Tony Luck" <tony.luck@gmail.com>
Subject: Re: [PATCH 0/1] mspec driver: compile error
Date: Wed, 08 Nov 2006 11:31:09 +0100 [thread overview]
Message-ID: <4551B1ED.2000405@sgi.com> (raw)
In-Reply-To: <20061108015618.571242fb.akpm@osdl.org>
Andrew Morton wrote:
> On Wed, 08 Nov 2006 18:45:30 +0900
> Fernando Luis Vázquez Cao <fernando@oss.ntt.co.jp> wrote:
>> On Wed, 2006-11-08 at 10:42 +0100, Jes Sorensen wrote:
>>> Given that MSPEC is clearly marked as depending on IA64, it seems bogus
>>> for i386 allmodconfig to barf over it and the problem should be fixed
>>> there instead IMHO.
>> Agreed. That is why I asked if that was allmodconfig's expected
>> behaviour. Andrew?
>
> kconfig's `select' isn't very smart. This is one of the reasons why one
> should avoid using it.
Hmmm, so what do we do? I really don't like the idea that one has to
manually select the uncached allocator in order for mspec to be
available.
Alternatively can move the Kconfig field for MSPEC to arch/ia64/Kconfig,
but that seems a bit dodgy too.
Cheers,
Jes
next prev parent reply other threads:[~2006-11-08 10:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 6:30 [PATCH 0/1] mspec driver: compile error Fernando Luis Vázquez Cao
2006-11-07 10:31 ` Jes Sorensen
2006-11-07 21:35 ` Andrew Morton
2006-11-08 9:19 ` Fernando Luis Vázquez Cao
2006-11-08 9:42 ` Jes Sorensen
2006-11-08 9:45 ` Fernando Luis Vázquez Cao
2006-11-08 9:56 ` Andrew Morton
2006-11-08 9:59 ` Fernando Luis Vázquez Cao
2006-11-08 10:31 ` Jes Sorensen [this message]
2006-11-08 10:52 ` Fernando Luis Vázquez Cao
2006-11-09 16:10 ` 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=4551B1ED.2000405@sgi.com \
--to=jes@sgi.com \
--cc=akpm@osdl.org \
--cc=bjorn_helgaas@hp.com \
--cc=dcn@sgi.com \
--cc=fernando@oss.ntt.co.jp \
--cc=holt@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=tony.luck@gmail.com \
--cc=torvalds@osdl.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