Re: [RFC 1/4] CONFIG_STABLE: Define it

[Sam Ravnborg <sam@ravnborg.org>]

On Fri, Jun 01, 2007 at 04:30:06PM -0400, Dave Jones wrote:
> On Fri, Jun 01, 2007 at 10:22:02PM +0200, Sam Ravnborg wrote:
>  > On Fri, Jun 01, 2007 at 02:02:00PM -0400, Dave Jones wrote:
>  > > On Thu, May 31, 2007 at 11:30:46PM +0200, Sam Ravnborg wrote:
>  > >  > > +	sym = sym_lookup("DEVEL_KERNEL", 0);
>  > >  > > +	sym->type = S_BOOLEAN;
>  > >  > > +	sym->flags |= SYMBOL_AUTO;
>  > >  > > +	p = getenv("DEVEL_KERNEL");
>  > >  > > +	if (p && atoi(p))
>  > >  > > +		sym_add_default(sym, "y");
>  > >  > > +	else
>  > >  > > +		sym_add_default(sym, "n");
>  > >  > > +
>  > >  > 
>  > >  > 		sym_set_tristate_value(sym, yes);
>  > >  > 	else
>  > >  > 		sym_set_tristate_value(sym, no);
>  > >  > 
>  > >  > should do the trick (untested).
>  > > 
>  > > Odd. What's the third state ? Undefined?
>  > no, mod, yes
>  > Representing: no, module, yes as the three config choices.
> 
> Now I'm even more puzzled.  Why would 'DEVEL_KERNEL' need
> to be modular ?
The same type is used to represent a boolean and a tristate
within kconfig:

typedef enum tristate {
	no, mod, yes
} tristate;

And in the cases where the config symbol is of type 'bool' then
the value 'mod' is not used.

	Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/