From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Konstantin Khlebnikov <khlebnikov@openvz.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: add config NUMA stub to all architectures
Date: Sat, 18 Feb 2012 10:39:14 +1100 [thread overview]
Message-ID: <20120218103914.39e7e1eb69e1fd29275c4849@canb.auug.org.au> (raw)
In-Reply-To: <20120217134404.GA11353@merkur.ravnborg.org>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
Hi Sam,
On Fri, 17 Feb 2012 14:44:04 +0100 Sam Ravnborg <sam@ravnborg.org> wrote:
>
> > Seems like Kconfig allow config option duplication, but it use default state from first.
> > If we add "config NUMA\n def_bool n" somewhere in generic Kconfig, default will be n if
> > Kconfig see this declaration first.
> Correct.
> And as n is default there is no need to specify it.
> But please add a help text that explain the symbol - even if it is not
> visible in menuconfig.
So does that mean that a simple
config NUMA
bool
help
some help text
in mm/Kconfig will have no effect on the defaults and dependencies if
"config NUMA" is specified elsewhere? (except to add the needed
__enabled_CONFIG_NUMA defines, of course). If that is the case, then
that is what we should add, right?
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-17 23:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 10:20 linux-next: build failure after merge of the final tree (akpm tree related) Stephen Rothwell
2012-02-17 12:06 ` Konstantin Khlebnikov
2012-02-17 12:08 ` [PATCH] mm: add config NUMA stub to all architectures Konstantin Khlebnikov
2012-02-17 12:45 ` Stephen Rothwell
2012-02-17 13:32 ` Konstantin Khlebnikov
2012-02-17 13:44 ` Sam Ravnborg
2012-02-17 23:39 ` Stephen Rothwell [this message]
2012-02-17 20:30 ` Andrew Morton
2012-02-19 17:01 ` Geert Uytterhoeven
2012-02-19 18:12 ` Randy Dunlap
2012-02-19 23:21 ` Arnaud Lacombe
2012-02-20 14:24 ` Michal Marek
2012-02-19 23:04 ` linux-next: build failure after merge of the final tree (akpm tree related) Stephen Rothwell
2012-02-19 23:15 ` Andrew Morton
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=20120218103914.39e7e1eb69e1fd29275c4849@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).