From: Badari Pulavarty <pbadari@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: randy.dunlap@oracle.com, linux-kernel@vger.kernel.org,
mingo@elte.hu, tglx@linutronix.de, lethal@linux-sh.org
Subject: Re: mmotm 2008-09-22-01-36 uploaded (memory_hotplug)
Date: Tue, 23 Sep 2008 16:14:52 -0700 [thread overview]
Message-ID: <1222211692.6491.12.camel@badari-desktop> (raw)
In-Reply-To: <20080923151748.7268cf16.akpm@linux-foundation.org>
On Tue, 2008-09-23 at 15:17 -0700, Andrew Morton wrote:
> On Tue, 23 Sep 2008 15:08:22 -0700
> Badari Pulavarty <pbadari@us.ibm.com> wrote:
>
> > > > so it is defined in both mm/memory_hotplug.c and
> > > > arch/x86/mm/init_64.c when CONFIG_MEMORY_HOTREMOVE=y.
> > > >
> > >
> > > OK, thanks, it looks like people are changing things under our feet.
> > >
> > > Badari, can you please check this fix against
> > > mm-cleanup-to-make-remove_memory-arch-neutral.patch?
> > >
> >
> >
> > When I made the patch, only ppc64, ia64 and s390 had
> > memory_remove() support in mainline. I sent a patch against
> > x86 to add hotplug memory remove support. I guess you
> > merged Gary's patch and sh-arch patch.
> >
> > I noticed that you cleaned up all these and added to -mm.
> > Do you want me to merge all these into a single patch and
> > resend it (against -mm) ?
>
> No, that's OK.
>
> > (It will look exactly the same
> > anyway).
>
> Does that mean you reviewed all the fixes I added? We're sure that all
> the per-arch implementations of remove_memory() can be replaced by the
> generic one?
Yes. I just reviewed all these patches in mmtom 2008-09-23.
They looked fine. There is no need for arch-specific ones.
Thanks,
Badari
prev parent reply other threads:[~2008-09-23 23:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200809220838.m8M8cwC2031790@imap1.linux-foundation.org>
2008-09-22 18:19 ` mmotm 2008-09-22-01-36 uploaded (kvm) Randy Dunlap
2008-09-22 19:52 ` Andrew Morton
2008-09-22 21:58 ` Jesse Barnes
2008-09-22 21:59 ` Jesse Barnes
2008-09-22 22:10 ` Andrew Morton
2008-09-23 6:32 ` Amit Shah
2008-09-23 10:25 ` Avi Kivity
2008-09-22 18:19 ` mmotm 2008-09-22-01-36 uploaded (profiling) Randy Dunlap
2008-09-22 19:50 ` Andrew Morton
2008-09-22 18:29 ` mmotm 2008-09-22-01-36 uploaded (memory_hotplug) Randy Dunlap
2008-09-22 19:57 ` Andrew Morton
2008-09-23 22:08 ` Badari Pulavarty
2008-09-23 22:17 ` Andrew Morton
2008-09-23 23:14 ` Badari Pulavarty [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=1222211692.6491.12.camel@badari-desktop \
--to=pbadari@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=tglx@linutronix.de \
/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