From: "Tim Pepper" <lnxninja@us.ibm.com>
To: "Dave Hansen" <haveblue@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
mkravetz@us.ibm.com, Arnd Bergmann <arnd@arndb.de>,
linux-mm@kvack.org, lkml <linux-kernel@vger.kernel.org>,
hch@infradead.org, External List <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>,
kmannth@us.ibm.com, gone@us.ibm.com,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [PATCH] Fix sparsemem on Cell (take 3)
Date: Sun, 7 Jan 2007 22:31:14 -0800 [thread overview]
Message-ID: <eada2a070701072231h6501fe9pcda8da51b1ecfb41@mail.gmail.com> (raw)
In-Reply-To: <1168160307.6740.9.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
On 1/7/07, Dave Hansen <haveblue@us.ibm.com> wrote:
>
> On Fri, 2007-01-05 at 22:52 -0600, John Rose wrote:
>
> > Could this break ia64, given that it uses memmap_init_zone()?
>
> You are right, I think it does.
>
> Here's an updated patch to replace the earlier one. I had to move the
> enum definition over to a different header because ia64 evidently has a
> different include order.
Boot tested OK on ia64 with this latest version of the patch.
Tim
[-- Attachment #2: Type: text/html, Size: 773 bytes --]
next prev parent reply other threads:[~2007-01-08 6:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 16:53 [PATCH] Fix sparsemem on Cell Dave Hansen
2006-12-15 17:11 ` Andy Whitcroft
2006-12-15 17:24 ` Dave Hansen
2006-12-15 19:45 ` Andrew Morton
2006-12-16 8:03 ` KAMEZAWA Hiroyuki
2006-12-18 21:13 ` Dave Hansen
2006-12-18 22:15 ` Christoph Hellwig
2006-12-18 22:54 ` Arnd Bergmann
2006-12-18 23:16 ` Dave Hansen
2006-12-19 0:16 ` KAMEZAWA Hiroyuki
2006-12-19 8:59 ` Arnd Bergmann
2006-12-19 19:34 ` Dave Hansen
2007-01-06 1:10 ` [PATCH] Fix sparsemem on Cell (take 3) Dave Hansen
2007-01-06 4:52 ` John Rose
2007-01-07 8:58 ` Dave Hansen
2007-01-07 12:07 ` Arnd Bergmann
2007-01-08 6:31 ` Tim Pepper [this message]
2007-01-08 6:47 ` Tim Pepper
2006-12-15 17:22 ` [PATCH] Fix sparsemem on Cell Michael Buesch
2006-12-15 17:57 ` Dave Hansen
2006-12-15 20:21 ` Benjamin Herrenschmidt
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=eada2a070701072231h6501fe9pcda8da51b1ecfb41@mail.gmail.com \
--to=lnxninja@us.ibm.com \
--cc=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=gone@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=hch@infradead.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kmannth@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mkravetz@us.ibm.com \
--cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).