From: Jes Sorensen <jes@sgi.com>
To: "Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>
Cc: Andrew Morton <akpm@osdl.org>,
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 10:42:02 +0100 [thread overview]
Message-ID: <4551A66A.2070506@sgi.com> (raw)
In-Reply-To: <1162977589.7805.77.camel@sebastian.intellilink.co.jp>
Fernando Luis Vázquez Cao wrote:
> On Tue, 2006-11-07 at 13:35 -0800, Andrew Morton wrote:
> The problem occurs because i386 (as expected) does not define
> IA64_UNCACHED_ALLOCATOR. I thought that making the select expression
> depend on IA64 as shown below might silence allmodconfig:
>
> select IA64_UNCACHED_ALLOCATOR if IA64
>
> But my guess was wrong and the same warning appeared. It seems that "if"
> expressions do not prevent allmodconfig from checking the symbol
> indicated by the select the "if" is conditioning. By the way, is this
> the expected behaviour? If so, we need to get rid of the reverse
> dependency, modify the "depends on" line accordingly, and make
> IA64_UNCACHED_ALLOCATOR selectable. I may be missing the whole point so
> please correct if I am wrong.
This patch is a bad solution as it requires people to manually select
the uncached allocator. It should be enabled automatically by MSPEC,
not the other way round.
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.
Cheers,
Jes
next prev parent reply other threads:[~2006-11-08 9:42 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 [this message]
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
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=4551A66A.2070506@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