From: Olaf Hering <olh@suse.de>
To: Andrew Morton <akpm@osdl.org>, linuxppc-dev@ozlabs.org
Subject: [PATCH] use Kconfig.hz
Date: Wed, 13 Jul 2005 15:55:25 +0200 [thread overview]
Message-ID: <20050713135525.GA18144@suse.de> (raw)
use new Kconfig.hz on ppc/ppc64, use also Kconfig.preempt for ppc
Signed-off-by: Olaf Hering <olh@suse.de>
arch/ppc/Kconfig | 12 ++----------
arch/ppc64/Kconfig | 1 +
2 files changed, 3 insertions(+), 10 deletions(-)
Index: linux-2.6.13-rc3-olh/arch/ppc/Kconfig
===================================================================
--- linux-2.6.13-rc3-olh.orig/arch/ppc/Kconfig
+++ linux-2.6.13-rc3-olh/arch/ppc/Kconfig
@@ -935,19 +935,11 @@ config NR_CPUS
depends on SMP
default "4"
-config PREEMPT
- bool "Preemptible Kernel"
- help
- This option reduces the latency of the kernel when reacting to
- real-time or interactive events by allowing a low priority process to
- be preempted even if it is in kernel mode executing a system call.
-
- Say Y here if you are building a kernel for a desktop, embedded
- or real-time system. Say N if you are unsure.
-
config HIGHMEM
bool "High memory support"
+source kernel/Kconfig.hz
+source kernel/Kconfig.preempt
source "mm/Kconfig"
source "fs/Kconfig.binfmt"
Index: linux-2.6.13-rc3-olh/arch/ppc64/Kconfig
===================================================================
--- linux-2.6.13-rc3-olh.orig/arch/ppc64/Kconfig
+++ linux-2.6.13-rc3-olh/arch/ppc64/Kconfig
@@ -288,6 +288,7 @@ config SCHED_SMT
overhead in some places. If unsure say N here.
source "kernel/Kconfig.preempt"
+source kernel/Kconfig.hz
config EEH
bool "PCI Extended Error Handling (EEH)" if EMBEDDED
next reply other threads:[~2005-07-13 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 13:55 Olaf Hering [this message]
2005-07-13 13:56 ` [PATCH] update ppc defconfigs Olaf Hering
2005-07-13 16:04 ` Tom Rini
2005-07-13 17:03 ` Olaf Hering
2005-07-13 18:02 ` Tom Rini
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=20050713135525.GA18144@suse.de \
--to=olh@suse.de \
--cc=akpm@osdl.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).