On Wed, Mar 14, 2007 at 10:30:31AM -0700, Linus Torvalds wrote: > > Nope. How can kconfig distinguish that from a boolean option in modular > > driver? bool *can* depend on tristate and be selected when tristate is > > set to m. > > Btw, this is one of those things that easily causes problems. > > In many ways it would be nice if we had two different kinds of "bool": one > where "m" in the dependency chain means "y" is ok, and one where "m" means > "n".
*nod* > Maybe not "bool" vs "mbool", but it might be nice to have > > bool FB_PS3 > depends strictly on FB > > ie a "depends strictly" refuses to upgrade a bool dependency from "m" to > "y", while a regular depends allows it. > > Or something.. The "depends strictly on X" thing would really be just a > mental shorthand for "depends on (X)=y" (it's actually longer to type, but > I think it's a bit more intuitive, thus "mental shortcut"). There's a fun side question, though: what should allmodconfig do? FB=m, FB_PS3=n? Or FB=y, FB_PS3=y? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
