From: Badari Pulavarty <pbadari@us.ibm.com>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
garyhade@us.ibm.com, linux-mm@kvack.org, mel@csn.ul.ie,
lcm@us.ibm.com, linux-kernel@vger.kernel.org, x86@kernel.org,
mingo@elte.hu
Subject: Re: [PATCH] Cleanup to make remove_memory() arch neutral
Date: Tue, 09 Sep 2008 08:12:52 -0700 [thread overview]
Message-ID: <1220973172.25932.68.camel@badari-desktop> (raw)
In-Reply-To: <20080909101703.C099.E1E9C6FF@jp.fujitsu.com>
On Tue, 2008-09-09 at 10:21 +0900, Yasunori Goto wrote:
> > On Mon, 08 Sep 2008 14:52:34 -0700
> > Badari Pulavarty <pbadari@us.ibm.com> wrote:
> >
> > > There is nothing architecture specific about remove_memory().
> > > remove_memory() function is common for all architectures which
> > > support hotplug memory remove. Instead of duplicating it in every
> > > architecture, collapse them into arch neutral function.
> > >
> > > Signed-off-by: Badari Pulavarty <pbadari@us.ibm.com>
> > >
> > > arch/ia64/mm/init.c | 17 -----------------
> > > arch/powerpc/mm/mem.c | 17 -----------------
> > > arch/s390/mm/init.c | 11 -----------
> > > mm/memory_hotplug.c | 10 ++++++++++
> > > 4 files changed, 10 insertions(+), 45 deletions(-)
> >
> > I spent some time trying to build-test this on ia64 and gave up. How
> > the heck do you turn on memory hotplug on ia64?
> >
>
> EXPORT_SYMBOL_GPL(remove_memory) is removed.
> It is required by drivers/acpi/acpi_memhotplug.ko.
Thanks for catching it. I forgot that it was being used
by acpi. Since we didn't export it for ppc and s390,
I assumed its safe to remove the export. Sorry !!
Thanks,
Badari
--
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>
next prev parent reply other threads:[~2008-09-09 15:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 17:21 [PATCH] [RESEND] x86_64: add memory hotremove config option Gary Hade
2008-09-05 17:44 ` Ingo Molnar
2008-09-05 18:14 ` Badari Pulavarty
2008-09-05 18:17 ` Ingo Molnar
2008-09-08 21:52 ` [PATCH] Cleanup to make remove_memory() arch neutral Badari Pulavarty
2008-09-09 0:56 ` Andrew Morton
2008-09-09 1:14 ` Randy Dunlap
2008-09-09 1:21 ` Yasunori Goto
2008-09-09 15:12 ` Badari Pulavarty [this message]
2008-09-08 21:56 ` [PATCH] x86: add memory hotremove config option Badari Pulavarty
2008-09-05 18:04 ` [PATCH] [RESEND] x86_64: " Andi Kleen
2008-09-05 18:31 ` Badari Pulavarty
2008-09-05 18:54 ` Andi Kleen
2008-09-05 22:34 ` Badari Pulavarty
2008-09-05 19:53 ` Gary Hade
2008-09-05 20:04 ` Andi Kleen
2008-09-05 21:54 ` Gary Hade
2008-09-06 0:01 ` Andi Kleen
2008-09-06 7:06 ` Yasunori Goto
2008-09-06 8:53 ` Andi Kleen
2008-09-08 5:52 ` Nick Piggin
2008-09-08 9:36 ` Andi Kleen
2008-09-08 9:46 ` Nick Piggin
2008-09-08 10:30 ` Andi Kleen
2008-09-08 11:19 ` Nick Piggin
2008-09-08 11:30 ` Andi Kleen
2008-09-08 13:48 ` Nick Piggin
2008-09-06 14:33 ` Ingo Molnar
2008-09-06 16:00 ` kamezawa.hiroyu
2008-09-06 16:17 ` Ingo Molnar
2008-09-06 16:05 ` kamezawa.hiroyu
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=1220973172.25932.68.camel@badari-desktop \
--to=pbadari@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=garyhade@us.ibm.com \
--cc=lcm@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
--cc=y-goto@jp.fujitsu.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