> Erik Andersen wrote:
>
>>I like this. It's simple, its clean, and it keeps all the
>>information in one spot. I think we can go a bit farther here
>>and add in a list of the .c files that enabling this feature
>>should add to the Makefile (per the current
>> obj-$(CONFIG_FOO) += foo.o
>>stuff in the current Makefile).
>
> Seriously, yep, that's exactly where we eventually want to be: all
> config, makefile, and help text info in one place. To add a new net
> driver, I want to be able to simply add two files, driver.c and
> driver.conf, and be done with it.
with kbuild-2.5 this can be done easy. We should maintain
the syntax of kbuild-2.5 (or a subset).
But the makefile/makefile.in will remain: not all code
in kernel is drivers, and for the non drivers makefile/config.in
IMHO it is better to have 'central' (per directory/per type)
config and makefile files.
giacomo
-
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/