From: Andy Whitcroft <apw@shadowen.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: David Miller <davem@davemloft.net>,
akpm@linux-foundation.org, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org, mbligh@google.com,
linux-mm@kvack.org, ak@suse.de, hansendc@us.ibm.com,
kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [PATCH 1/4] Generic Virtual Memmap suport for SPARSEMEM V3
Date: Tue, 10 Apr 2007 11:43:43 +0100 [thread overview]
Message-ID: <461B6A5F.3020007@shadowen.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0704051525350.15901@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> On Thu, 5 Apr 2007, David Miller wrote:
>
>> Hey Christoph, here is sparc64 support for this stuff.
>
> Great!
>
>> After implementing this and seeing more and more how it works, I
>> really like it :-)
>>
>> Thanks a lot for doing this work Christoph!
>
> Thanks for the appreciation. CCing Andy Whitcroft who will hopefully
> merge this all of this together into sparsemem including the S/390
> implementation.
Yep grabbed this one and added it to the stack. Now to find a sparc to
test it with!
-apw
--
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:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-04-10 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 23:06 Christoph Lameter
2007-04-04 23:06 ` [PATCH 2/4] x86_64: SPARSE_VIRTUAL 2M page size support Christoph Lameter
2007-04-04 23:06 ` [PATCH 3/4] IA64: SPARSE_VIRTUAL 16K " Christoph Lameter
2007-04-04 23:06 ` [PATCH 4/4] IA64: SPARSE_VIRTUAL 16M " Christoph Lameter
2007-04-05 22:50 ` Luck, Tony
2007-04-05 23:10 ` David Miller, Luck, Tony
2007-04-06 17:16 ` Christoph Lameter
2007-04-05 21:29 ` [PATCH 1/4] Generic Virtual Memmap suport for SPARSEMEM V3 David Miller, Christoph Lameter
2007-04-05 22:27 ` Christoph Lameter
2007-04-10 10:43 ` Andy Whitcroft [this message]
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=461B6A5F.3020007@shadowen.org \
--to=apw@shadowen.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=davem@davemloft.net \
--cc=hansendc@us.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@google.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