From: Sam Ravnborg <[EMAIL PROTECTED]> Date: Wed, 13 Feb 2008 09:45:41 +0100
> So we could do: > > config foo > tristate "do you want foo?" > depends on USB && BAR > module > obj-$(CONFIG_FOO) += foo.o > foo-y := file1.o file2.o > help > foo will allow you to explode your PC ... > Does this fit what you had in mind? Yes it does. Now I'll ask if you think embedding this information in one of the C files for a module would be even nicer? Also, we need to make sure we can properly handle top-level container-like items. For example, where would menuconfigs like NETDEV_10000 go if we adopt this kind of scheme? -- 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/
