From: Randy Dunlap <rdunlap@xenotime.net>
To: lkml <linux-kernel@vger.kernel.org>
Cc: akpm <akpm@osdl.org>, 76306.1226@compuserve.com, ebiederm@xmission.com
Subject: [PATCH] fix EMBEDDED + SYSCTL menu
Date: Thu, 28 Sep 2006 20:42:51 -0700 [thread overview]
Message-ID: <20060928204251.a20470c5.rdunlap@xenotime.net> (raw)
From: Randy Dunlap <rdunlap@xenotime.net>
SYSCTL should still depend on EMBEDDED. This unbreaks the
EMBEDDED menu (from the recent SYSCTL_SYCALL menu option patch).
Fix typos in new SYSCTL_SYSCALL menu.
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
init/Kconfig | 14 +++++++-------
1 files changed, 7 insertions(+), 7 deletions(-)
--- linux-2618-g10.orig/init/Kconfig
+++ linux-2618-g10/init/Kconfig
@@ -257,6 +257,9 @@ config CC_OPTIMIZE_FOR_SIZE
If unsure, say N.
+config SYSCTL
+ bool
+
menuconfig EMBEDDED
bool "Configure standard kernel features (for small systems)"
help
@@ -272,11 +275,8 @@ config UID16
help
This enables the legacy 16-bit UID syscall wrappers.
-config SYSCTL
- bool
-
config SYSCTL_SYSCALL
- bool "Sysctl syscall support"
+ bool "Sysctl syscall support" if EMBEDDED
default n
select SYSCTL
---help---
@@ -285,11 +285,11 @@ config SYSCTL_SYSCALL
and use. The interface in /proc/sys is now the primary and what
everyone uses.
- Nothing has been using the binary sysctl interface for some time
+ Nothing has been using the binary sysctl interface for some
time now so nothing should break if you disable sysctl syscall
- support, and you kernel will get marginally smaller.
+ support, and your kernel will get marginally smaller.
- Unless you have an application that uses the sys_syscall interface
+ Unless you have an application that uses the sys_sysctl interface
you should probably say N here.
config KALLSYMS
---
next reply other threads:[~2006-09-29 3:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 3:42 Randy Dunlap [this message]
2006-09-29 16:05 ` Adrian Bunk
2006-09-29 16:24 ` Randy Dunlap
2006-09-30 0:55 ` Eric W. Biederman
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=20060928204251.a20470c5.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--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
all inboxes | Powered by JetHome®