All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@mvista.com>
To: linux-kernel@vger.kernel.org
Cc: anton@au.ibm.com
Subject: [patch] ppc64 configure option fix
Date: Tue, 04 Nov 2003 00:05:51 -0500	[thread overview]
Message-ID: <1067922350.17109.41.camel@localhost> (raw)

Hi, Anton.

arch/ppc64/Kconfig's entry for CONFIG_PREEMPT is missing the description
after the "bool" statement, so the entry does not show up.

Also, the help description mentions a restriction that is not [any
longer] true.

Patch against 2.6.0-test9.

	Robert Love


 arch/ppc64/Kconfig |    5 +----
 1 files changed, 1 insertion(+), 4 deletions(-)

diff -urN linux-2.6.0-test9/arch/ppc64/Kconfig linux/arch/ppc64/Kconfig
--- linux-2.6.0-test9/arch/ppc64/Kconfig	2003-10-25 14:43:47.000000000 -0400
+++ linux/arch/ppc64/Kconfig	2003-11-03 23:53:54.000000000 -0500
@@ -113,14 +113,11 @@
 	depends on DISCONTIGMEM
 
 config PREEMPT
-	bool
+	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.
-	  Unfortunately the kernel code has some race conditions if both
-	  CONFIG_SMP and CONFIG_PREEMPT are enabled, so this option is
-	  currently disabled if you are building an SMP kernel.
 
 	  Say Y here if you are building a kernel for a desktop, embedded
 	  or real-time system.  Say N if you are unsure.



                 reply	other threads:[~2003-11-04  5:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1067922350.17109.41.camel@localhost \
    --to=rml@mvista.com \
    --cc=anton@au.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.