path: root/init/Kconfig
diff options
authorYann E. MORIN <>2013-08-11 16:07:50 +0200
committerYann E. MORIN <>2013-08-15 22:56:08 +0200
commit11097a0367e48954ecf616f9b0df48d86835dd0d (patch)
treea795726b62f68894fad0cc251e43d404f82d4aff /init/Kconfig
parent04b19b773a60d201bc1b187ba7a7c86dc237a27b (diff)
modules: do not depend on kconfig to set 'modules' option to symbol MODULES
Currently, the MODULES symbol is special-cased in different places in the kconfig language. For example, if no symbol is defined to enable tristates, then kconfig looks up for a symbol named 'MODULES', and forces the 'modules' option onto that symbol. This causes problems as such: - since MODULES is special-cased, reading the configuration with KCONFIG_ALLCONFIG set will forcibly set MODULES to be 'valid' (ie. it has a valid value), when no such value was previously set. So MODULES defaults to 'n' unless it is present in KCONFIG_ALLCONFIG - other third-party projects may decide that 'MODULES' plays a different role for them This has been exposed by cset #cfa98f2e: kconfig: do not override symbols already set and reported by Stephen in: As suggested by Sam, we explicitly define the MODULES symbol to be the tristate-enabler. This will allow us to drop special-casing of MODULES in the kconfig language, later. (Note: this patch is not a fix to Stephen's issue, just a first step). Reported-by: Stephen Rothwell <> Signed-off-by: Cc: Stephen Rothwell <> Cc: Sam Ravnborg <> Cc: Michal Marek <> Cc: Kevin Hilman <> Cc: Cc: Theodore Ts'o <>
Diffstat (limited to 'init/Kconfig')
1 files changed, 1 insertions, 0 deletions
diff --git a/init/Kconfig b/init/Kconfig
index 247084b..4d55e81 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -1666,6 +1666,7 @@ config BASE_SMALL
menuconfig MODULES
bool "Enable loadable module support"
+ option modules
Kernel modules are small pieces of compiled code which can
be inserted in the running kernel, rather than being