public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: [rfc] fix Kconfig, hotplug_cpu is needed for swsusp
Date: Thu, 30 Mar 2006 00:08:08 +0200	[thread overview]
Message-ID: <20060329220808.GA1716@elf.ucw.cz> (raw)

HOTPLUG_CPU is needed on normal PCs, too -- it is neccessary for
software suspend.

Signed-off-by: Pavel Machek <pavel@suse.cz>

---
commit 2206dab43d50723d6b15caa8821e8d97c6b5ef28
tree cbfc324e15d216aa91ce6a51927668076de5b7db
parent dd76aabd03933b80c61fa5b0c0c995950246c603
author <pavel@amd.ucw.cz> Thu, 30 Mar 2006 00:06:31 +0200
committer <pavel@amd.ucw.cz> Thu, 30 Mar 2006 00:06:31 +0200

 arch/i386/Kconfig      |    8 ++++----
 kernel/power/process.c |    3 +--
 kernel/signal.c        |    1 +
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/arch/i386/Kconfig b/arch/i386/Kconfig
index f7db71d..955dc08 100644
--- a/arch/i386/Kconfig
+++ b/arch/i386/Kconfig
@@ -741,12 +741,12 @@ config PHYSICAL_START
 
 config HOTPLUG_CPU
 	bool "Support for hot-pluggable CPUs (EXPERIMENTAL)"
-	depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER && !X86_PC
+	depends on SMP && HOTPLUG && EXPERIMENTAL && !X86_VOYAGER
 	---help---
-	  Say Y here to experiment with turning CPUs off and on.  CPUs
-	  can be controlled through /sys/devices/system/cpu.
+	  Say Y here to experiment with turning CPUs off and on, and to 
+	  enable suspend on SMP systems. CPUs can be controlled through
+	  /sys/devices/system/cpu.
 
-	  Say N.
 
 config DOUBLEFAULT
 	default y

-- 
Picture of sleeping (Linux) penguin wanted...

             reply	other threads:[~2006-03-29 22:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29 22:08 Pavel Machek [this message]
2006-03-29 22:47 ` [rfc] fix Kconfig, hotplug_cpu is needed for swsusp Andrew Morton
2006-03-29 23:09   ` Ashok Raj
2006-03-29 23:36     ` Nigel Cunningham
2006-03-29 23:47       ` Ashok Raj
2006-03-29 23:53         ` Nigel Cunningham
2006-03-30  0:12           ` Ashok Raj
2006-03-30  0:32             ` Nigel Cunningham
2006-03-30  0:13           ` Andrew Morton
2006-03-30  0:18             ` Nigel Cunningham
2006-03-30  3:01               ` Nigel Cunningham
     [not found]                 ` <20060330030657.GA10405@mars.ravnborg.org>
2006-03-30 10:11                   ` Roman Zippel
2006-03-30  8:24           ` Jan Engelhardt
2006-04-04  5:15             ` menuconfig search (Re: [rfc] fix Kconfig, hotplug_cpu is needed for swsusp) Randy.Dunlap
2006-04-04  6:01               ` Alexey Dobriyan
2006-04-04 15:12                 ` Randy.Dunlap
2006-04-08  8:42               ` Jan Engelhardt
2006-04-09  2:29                 ` Randy.Dunlap
2006-04-11 11:18                   ` Jan Engelhardt
2006-03-30  8:41         ` [rfc] fix Kconfig, hotplug_cpu is needed for swsusp Pavel Machek
2006-03-30 16:17           ` Rafael J. Wysocki
2006-03-29  0:30             ` Pavel Machek
2006-04-01 23:55               ` Ashok Raj
2006-03-30  3:24     ` Andrew Morton
2006-03-30 13:00       ` Ashok Raj
2006-03-30 13:17         ` Pavel Machek
2006-03-30 13:05       ` Eric W. Biederman
2006-03-30  8:30     ` Pavel Machek

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=20060329220808.GA1716@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --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