[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120218103914.39e7e1eb69e1fd29275c4849@canb.auug.org.au>
Date: Sat, 18 Feb 2012 10:39:14 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Sam Ravnborg <sam@...nborg.org>
Cc: Konstantin Khlebnikov <khlebnikov@...nvz.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm: add config NUMA stub to all architectures
Hi Sam,
On Fri, 17 Feb 2012 14:44:04 +0100 Sam Ravnborg <sam@...nborg.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@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists