From: Alexander Holler <holler@ahsoftware.de>
To: linux-kernel@vger.kernel.org
Cc: Alexander Holler <holler@ahsoftware.de>
Subject: [PATCH] Make IKCONFIG an embedded option, enabled by default
Date: Wed, 25 Jul 2012 05:53:36 +0200 [thread overview]
Message-ID: <1343188416-7742-1-git-send-email-holler@ahsoftware.de> (raw)
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 <holler@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
next reply other threads:[~2012-07-25 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 3:53 Alexander Holler [this message]
2012-07-25 9:52 ` [PATCH] Make IKCONFIG an embedded option, enabled by default Alexander Holler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1343188416-7742-1-git-send-email-holler@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox