From: Dave Hansen <haveblue@us.ibm.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Bob Picco <bob.picco@hp.com>, Andrew Morton <akpm@osdl.org>,
linux-arch@vger.kernel.org, Andy Whitcroft <apw@shadowen.org>,
"Tolentino, Matthew E" <matthew.e.tolentino@intel.com>
Subject: RE: sparsemem patches in -mm
Date: Tue, 21 Jun 2005 09:17:32 -0700 [thread overview]
Message-ID: <1119370652.27442.39.camel@localhost> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F03BF854E@scsmsx401.amr.corp.intel.com>
On Tue, 2005-06-21 at 09:09 -0700, Luck, Tony wrote:
> >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?
>
> Without the extreme code, I'll have a hard time putting together a
> practical generic config for ia64. When you say "a couple more releases",
> are you referring to "-mm" releases, or Linus releases?
Just -mm. I think it's only been in one -mm release so far. The rest
of sparsemem has been in -mm since early May.
I have memory hotplug working on top of the extreme patches as well now,
which required a few more tweaks. That kind of tweaking needs to be
completed by the time it's submitted to mainline, and it's just not
quite there yet. I'm sure it will be soon.
-- Dave
next prev parent reply other threads:[~2005-06-21 16:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 16:09 sparsemem patches in -mm Luck, Tony
2005-06-21 16:17 ` Dave Hansen [this message]
-- 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 9:13 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
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
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=1119370652.27442.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=tony.luck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox