From: akpm@linux-foundation.org
To: pavel@suse.cz, haveblue@us.ibm.com,
matthew.e.tolentino@intel.com, rjw@sisk.pl,
y-goto@jp.fujitsu.com, mm-commits@vger.kernel.org
Subject: - hibernation-should-work-ok-with-memory-hotplug.patch removed from -mm tree
Date: Mon, 03 Nov 2008 13:46:42 -0800 [thread overview]
Message-ID: <200811032146.mA3LkhEd018236@imap1.linux-foundation.org> (raw)
The patch titled
hibernation should work ok with memory hotplug
has been removed from the -mm tree. Its filename was
hibernation-should-work-ok-with-memory-hotplug.patch
This patch was dropped because it is premature
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: hibernation should work ok with memory hotplug
From: Pavel Machek <pavel@suse.cz>
hibernation + memory hotplug was disabled in kconfig because we could
not handle hibernation + sparse mem at some point. It seems to work
now, so I guess we can enable it.
Signed-off-by: Pavel Machek <pavel@suse.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Matt Tolentino <matthew.e.tolentino@intel.com>
Cc: Dave Hansen <haveblue@us.ibm.com>
Cc: Yasunori Goto <y-goto@jp.fujitsu.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/Kconfig | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff -puN mm/Kconfig~hibernation-should-work-ok-with-memory-hotplug mm/Kconfig
--- a/mm/Kconfig~hibernation-should-work-ok-with-memory-hotplug
+++ a/mm/Kconfig
@@ -128,12 +128,9 @@ config SPARSEMEM_VMEMMAP
config MEMORY_HOTPLUG
bool "Allow for memory hot-add"
depends on SPARSEMEM || X86_64_ACPI_NUMA
- depends on HOTPLUG && !HIBERNATION && ARCH_ENABLE_MEMORY_HOTPLUG
+ depends on HOTPLUG && ARCH_ENABLE_MEMORY_HOTPLUG
depends on (IA64 || X86 || PPC64 || SUPERH || S390)
-comment "Memory hotplug is currently incompatible with Software Suspend"
- depends on SPARSEMEM && HOTPLUG && HIBERNATION
reply other threads:[~2008-11-03 21:47 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=200811032146.mA3LkhEd018236@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=mm-commits@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
--cc=y-goto@jp.fujitsu.com \
/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.