The exact semantics are:
.config:
CONFIG_FOO=y # yes
CONFIG_FOO=m # module
# CONFIG_FOO is not set # no
include/linux/autoconf.h:
#define CONFIG_FOO 1 /* yes */
#undef CONFIG_FOO /* module */
#define CONFIG_FOO_MODULE 1 /* module */
#undef CONFIG_FOO /* no */
So anything in C code that tests for CONFIG_FOO is going to be true
if FOO is configured 'yes' and false if FOO is configured 'module'.
I think some kernel code suffers from a misapprehension that CONFIG_FOO
is enabled for both 'yes' and 'module'. It's only enabled for 'yes'.
Michael Elizabeth Chastain
<mailto:mec@shout.net>
"love without fear"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 21:00:16 EST