From: Dave Hansen <haveblue@us.ibm.com>
To: Bob Picco <bob.picco@hp.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-arch@vger.kernel.org, Andy Whitcroft <apw@shadowen.org>,
Matt Tolentino <matthew.e.tolentino@intel.com>
Subject: Re: sparsemem patches in -mm
Date: Tue, 21 Jun 2005 08:57:56 -0700 [thread overview]
Message-ID: <1119369476.27442.30.camel@localhost> (raw)
In-Reply-To: <20050621110006.GH23911@localhost.localdomain>
On Tue, 2005-06-21 at 07:00 -0400, Bob Picco wrote:
> Andrew Morton wrote: [Tue Jun 21 2005, 05:13:52AM EDT]
> >
> > Could I ask the arch maintainers to review the `sparsemem' patches from -mm,
> > please, if you haven't done so...
> >
> Well ia64 SPARSEMEM hasn't been accepted yet by ia64. I did test
> SPARSEMEM with recent -mm patches on ia64 (EXTREME) and x86_64 4 way
> Opteron (!EXTREME) with OSDL aim.
I think the whole set is just about ready for mainline. If anybody
wants a consolidated set of patches that's easier to review, that's no
problem.
I'd only suggest that we keep the "extreme" stuff in -mm for a couple
more releases. It's a pretty clean add-on, and it has only had a very
short time in -mm. Bob, would you agree?
-- Dave
next prev parent reply other threads:[~2005-06-21 15:58 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 [this message]
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
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=1119369476.27442.30.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 \
/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.