From: Adrian Bunk <bunk@stusta.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
76306.1226@compuserve.com, ebiederm@xmission.com
Subject: Re: [PATCH] fix EMBEDDED + SYSCTL menu
Date: Fri, 29 Sep 2006 18:05:21 +0200 [thread overview]
Message-ID: <20060929160521.GF3469@stusta.de> (raw)
In-Reply-To: <20060928204251.a20470c5.rdunlap@xenotime.net>
On Thu, Sep 28, 2006 at 08:42:51PM -0700, Randy Dunlap wrote:
> 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
> -
ACK
> config SYSCTL_SYSCALL
> - bool "Sysctl syscall support"
> + bool "Sysctl syscall support" if EMBEDDED
> default n
> select SYSCTL
> ---help---
>...
You could achieve the same by removing the option...
Simply move SYSCTL_SYSCALL to the same place you are moving SYSCTL to
without fiddling with the dependencies.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-09-29 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 3:42 Randy Dunlap
2006-09-29 16:05 ` Adrian Bunk [this message]
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=20060929160521.GF3469@stusta.de \
--to=bunk@stusta.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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®