From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Ben Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org
Subject: Re: [BUGFIX][mmotm] fix walk system ram range patch (Was Re: mmotm on powerpc: walk_memory_resource?
Date: Wed, 16 Sep 2009 16:25:54 +0800 [thread overview]
Message-ID: <2375c9f90909160125t20b8cce0w18dddbccdf2010a@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0909152315380.25569@chino.kir.corp.google.com>
On Wed, Sep 16, 2009 at 2:16 PM, David Rientjes <rientjes@google.com> wrote:
> On Wed, 16 Sep 2009, KAMEZAWA Hiroyuki wrote:
>
>> Index: mmotm-2.6.31-Sep14/arch/powerpc/mm/mem.c
>> ===================================================================
>> --- mmotm-2.6.31-Sep14.orig/arch/powerpc/mm/mem.c
>> +++ mmotm-2.6.31-Sep14/arch/powerpc/mm/mem.c
>> @@ -166,7 +166,7 @@ walk_system_ram_range(unsigned long star
>> }
>> return ret;
>> }
>> -EXPORT_SYMBOL_GPL(walk_memory_resource);
>> +EXPORT_SYMBOL_GPL(walk_system_ram_range);
>>
>> /*
>> * Initialize the bootmem system and give it all the memory we
>>
>
> Um, doesn't drivers/infiniband/hw/ehca/ehca_mrmw.c need to be fixed too?
Yes, all callers of walk_memory_resource() should be fixed.
next prev parent reply other threads:[~2009-09-16 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 21:36 Hugh Dickins
2009-09-15 23:53 ` KAMEZAWA Hiroyuki
2009-09-16 0:26 ` [BUGFIX][mmotm] fix walk system ram range patch (Was " KAMEZAWA Hiroyuki
2009-09-16 6:16 ` David Rientjes
2009-09-16 6:44 ` [BUGFIX] fix walk systm ram range for infiniband (Was " KAMEZAWA Hiroyuki
2009-09-16 8:25 ` Américo Wang [this message]
2009-09-16 8:25 ` Américo Wang
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=2375c9f90909160125t20b8cce0w18dddbccdf2010a@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@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
all inboxes | Powered by JetHome®