From: Dave Hansen <haveblue@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Keith Mannthey <kmannth@us.ibm.com>,
linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/5] prepare x86/ppc64 DISCONTIG code for hotplug
Date: Mon, 28 Feb 2005 10:54:18 -0800 [thread overview]
Message-ID: <1109616858.6921.39.camel@localhost> (raw)
Subject pretty much says it all. Descriptions are in the individual
patches. These patches replace the
"allow-hot-add-enabled-i386-numa-box-to-boot.patch" which is currently
in -mm. Please drop it.
They apply to 2.6.11-rc5 after a few patches from -mm which conflicted:
stop-using-base-argument-in-__free_pages_bulk.patch
consolidate-set_max_mapnr_init-implementations.patch
refactor-i386-memory-setup.patch
remove-free_all_bootmem-define.patch
mostly-i386-mm-cleanup.patch
Boot-tested on plain x86 laptop, NUMAQ, and Summit. These probably
deserve to stay in -mm for a release or two.
-- Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Keith Mannthey <kmannth@us.ibm.com>,
linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/5] prepare x86/ppc64 DISCONTIG code for hotplug
Date: Mon, 28 Feb 2005 10:54:18 -0800 [thread overview]
Message-ID: <1109616858.6921.39.camel@localhost> (raw)
Subject pretty much says it all. Descriptions are in the individual
patches. These patches replace the
"allow-hot-add-enabled-i386-numa-box-to-boot.patch" which is currently
in -mm. Please drop it.
They apply to 2.6.11-rc5 after a few patches from -mm which conflicted:
stop-using-base-argument-in-__free_pages_bulk.patch
consolidate-set_max_mapnr_init-implementations.patch
refactor-i386-memory-setup.patch
remove-free_all_bootmem-define.patch
mostly-i386-mm-cleanup.patch
Boot-tested on plain x86 laptop, NUMAQ, and Summit. These probably
deserve to stay in -mm for a release or two.
-- Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next reply other threads:[~2005-02-28 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 18:54 Dave Hansen [this message]
2005-02-28 18:54 ` [PATCH 0/5] prepare x86/ppc64 DISCONTIG code for hotplug Dave Hansen
2005-03-01 0:42 ` Andrew Morton
2005-03-01 0:42 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2005-02-24 17:30 Dave Hansen
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=1109616858.6921.39.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=kmannth@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.