From: Dave Hansen <haveblue@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Andy Whitcroft <apw@shadowen.org>,
matthew@wil.cx, linux-arch@vger.kernel.org,
Matthew E Tolentino <matthew.e.tolentino@intel.com>,
Bob Picco <bob.picco@hp.com>
Subject: Re: sparsemem patches in -mm
Date: Tue, 21 Jun 2005 16:39:36 -0700 [thread overview]
Message-ID: <1119397176.18457.39.camel@localhost> (raw)
In-Reply-To: <20050621130150.62fbd353.akpm@osdl.org>
On Tue, 2005-06-21 at 13:01 -0700, Andrew Morton wrote:
> The patches I have there seem fairly logical, although there's a lot of
> Kconfig futzing going on. Do you spy any patches which should be collapsed
> together there? If so, which?
I've broken the mm/Kconfig ones up into four parts, each using the title
of the first one in the set that was combined. There was a bit of
unnecessary context that required rediffing.
The resultant four patches can be found here:
http://sr71.net/~dave/sparsemem/all-condensed/
I'd be happy to post these to LKML or linux-arch if anyone wants to see
them in normal emailed patch form.
order:
create-mm-kconfig-for-arch-independent-memory-options.patch
make-each-arch-use-mm-kconfig.patch
update-all-defconfigs-for-arch_discontigmem_enable.patch
introduce-new-kconfig-option-for-numa-or-discontig.patch
Applied, they produce the exact same output as the source nine patches
from 2.6.12-mm1:
> create-mm-kconfig-for-arch-independent-memory-options.patch
> make-each-arch-use-mm-kconfig.patch
> make-each-arch-use-mm-kconfig-fix.patch
> update-all-defconfigs-for-arch_discontigmem_enable.patch
> introduce-new-kconfig-option-for-numa-or-discontig.patch
> sparsemem-fix-minor-defaults-issue-in-mm-kconfig.patch
> mm-kconfig-kill-unused-arch_flatmem_disable.patch
> mm-kconfig-hide-memory-model-selection-menu.patch
> mm-kconfig-give-discontig-more-help-text.patch
Into this order, in these groups:
create-mm-kconfig-for-arch-independent-memory-options.patch
sparsemem-fix-minor-defaults-issue-in-mm-kconfig.patch
mm-kconfig-hide-memory-model-selection-menu.patch
mm-kconfig-give-discontig-more-help-text.patch
#
make-each-arch-use-mm-kconfig.patch
mm-kconfig-kill-unused-arch_flatmem_disable.patch
make-each-arch-use-mm-kconfig-fix.patch
#
update-all-defconfigs-for-arch_discontigmem_enable.patch
#
introduce-new-kconfig-option-for-numa-or-discontig.patch
-- Dave
next prev parent reply other threads:[~2005-06-21 23:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 9:13 sparsemem patches in -mm Andrew Morton
2005-06-21 9:50 ` Andi Kleen
2005-06-21 10:09 ` Andrew Morton
2005-06-21 15:49 ` Andy Whitcroft
2005-06-21 15:58 ` Andi Kleen
2005-06-21 11:00 ` Bob Picco
2005-06-21 15:57 ` Dave Hansen
2005-06-21 16:45 ` Bob Picco
2005-06-21 14:17 ` Matthew Wilcox
2005-06-21 15:51 ` Andy Whitcroft
2005-06-21 20:01 ` Andrew Morton
2005-06-21 23:39 ` Dave Hansen [this message]
2005-06-22 5:46 ` David S. Miller
2005-06-22 6:00 ` Andrew Morton
2005-07-27 22:42 ` David S. Miller
2005-06-23 22:48 ` Roman Zippel
2005-06-23 22:56 ` Dave Hansen
2005-06-23 23:53 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2005-06-21 15:52 Luck, Tony
2005-06-21 15:58 ` Andy Whitcroft
2005-06-21 16:09 Luck, Tony
2005-06-21 16:17 ` 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=1119397176.18457.39.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=bob.picco@hp.com \
--cc=linux-arch@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=matthew@wil.cx \
/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