From: "Martin J. Bligh" <mbligh@mbligh.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] some fixups for the X86_NUMAQ dependencies
Date: Mon, 20 Feb 2006 09:39:38 -0800 [thread overview]
Message-ID: <43F9FEDA.3030205@mbligh.org> (raw)
In-Reply-To: <20060220170827.GD4661@stusta.de>
>>>config X86_NUMAQ
>>> bool "NUMAQ (IBM/Sequent)"
>>>+ select SMP
>>> select NUMA
>>> help
>>> This option is used for getting Linux to run on a (IBM/Sequent)
>>> NUMA
>>>@@ -419,6 +420,7 @@
>>
>>Surely NUMA should select SMP, not NUMA-Q?
>
> NUMA depends on SMP.
>
> Therefore, if you select NUMA, you have to ensure that SMP is enabled.
Yes. but that should link SMP -> NUMA -> NUMA-Q, not SMP directly to
NUMA-Q, surely?
> NUMAQ can't be hidden since it doesn't has any dependencies.
> And this isn't what this comment is talking about (note the the
> comment is only shown if NUMAQ was already select'ed).
>
> NUMAQ didn't fulfill the contract that when select'ing NUMA, it has to
> ensure the dependencies of NUMA are fulfilled. My patch solves this
> properly instead of telling the user through a comment that he ran into
> this bug.
Yes, if that works, it's much cleaner. Perhaps we just had insufficient
config-fu to figure it out ... it looks good - I suppose I'd better test
it, and make sure we don't hit the same thing we did before.
m.
next prev parent reply other threads:[~2006-02-20 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-19 23:26 [2.6 patch] some fixups for the X86_NUMAQ dependencies Adrian Bunk
2006-02-20 16:33 ` Martin J. Bligh
2006-02-20 17:08 ` Adrian Bunk
2006-02-20 17:39 ` Martin J. Bligh [this message]
2006-02-20 17:48 ` Adrian Bunk
2006-03-03 21:34 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2006-03-09 23:06 Adrian Bunk
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=43F9FEDA.3030205@mbligh.org \
--to=mbligh@mbligh.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.