[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070913194130.1611fd78.akpm@linux-foundation.org>
Date: Thu, 13 Sep 2007 19:41:30 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Yasunori Goto <y-goto@...fujitsu.com>
Cc: Andy Whitcroft <apw@...dowen.org>,
Paul Mundt <lethal@...ux-sh.org>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH -mm] mm: Fix memory hotplug + sparsemem build.
On Fri, 14 Sep 2007 11:02:43 +0900 Yasunori Goto <y-goto@...fujitsu.com> wrote:
> > > /* call arch's memory hotadd */
> > >
> >
> > OK, we're getting into a mess here. This patch fixes
> > update-n_high_memory-node-state-for-memory-hotadd.patch, but which patch
> > does update-n_high_memory-node-state-for-memory-hotadd.patch fix?
> >
> > At present I just whacked
> > update-n_high_memory-node-state-for-memory-hotadd.patch at the end of
> > everything, but that was lazy of me and it ends up making a mess.
>
> It is enough. No more patch is necessary for these issues.
> I already fixed about Andy-san's comment. :-)
Now I'm more confused. I have two separeate questions:
a) Is the justr-added update-n_high_memory-node-state-for-memory-hotadd-fix.patch
still needed?
b) Which patch in 2.6.22-rc4-mm1 does
update-n_high_memory-node-state-for-memory-hotadd.patch fix? In other
words, into which patch should I fold
update-n_high_memory-node-state-for-memory-hotadd.patch prior to sending
to Linus?
(I (usually) get to work this out for myself. Sometimes it is painful).
Generally, if people tell me which patch-in-mm their patch is fixing,
it really helps. Adrian does this all the time.
Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists