Knowing (being sure) which configuration was used to build a (maybe running)
kernel is important for many scenarios.

It's usually much more important than saving a few kb in the size of
the kernel. Therefor turn on CONFIG_IKCONFIG and CONFIG_IKCONFIG_PROC
by default and make them visible only when CONFIG_EMBEDDED is enabled,
preventing premature optimization.

Signed-off-by: Alexander Holler <hol...@ahsoftware.de>
---
 init/Kconfig |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/init/Kconfig b/init/Kconfig
index d07dcf9..f468b03 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -583,7 +583,8 @@ config RCU_BOOST_DELAY
 endmenu # "RCU Subsystem"
 
 config IKCONFIG
-       tristate "Kernel .config support"
+       tristate "Kernel .config support" if EMBEDDED
+       default y
        ---help---
          This option enables the complete Linux kernel ".config" file
          contents to be saved in the kernel. It provides documentation
@@ -595,8 +596,9 @@ config IKCONFIG
          /proc/config.gz if enabled (below).
 
 config IKCONFIG_PROC
-       bool "Enable access to .config through /proc/config.gz"
+       bool "Enable access to .config through /proc/config.gz" if EMBEDDED
        depends on IKCONFIG && PROC_FS
+       default y
        ---help---
          This option enables access to the kernel configuration file
          through /proc/config.gz.
-- 
1.7.6.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to