From: Andrew Morton <akpm@linux-foundation.org>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: Andy Whitcroft <apw@shadowen.org>,
Paul Mundt <lethal@linux-sh.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH -mm] mm: Fix memory hotplug + sparsemem build.
Date: Thu, 13 Sep 2007 19:41:30 -0700 [thread overview]
Message-ID: <20070913194130.1611fd78.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070914105420.F2E9.Y-GOTO@jp.fujitsu.com>
On Fri, 14 Sep 2007 11:02:43 +0900 Yasunori Goto <y-goto@jp.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.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: Andy Whitcroft <apw@shadowen.org>,
Paul Mundt <lethal@linux-sh.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH -mm] mm: Fix memory hotplug + sparsemem build.
Date: Thu, 13 Sep 2007 19:41:30 -0700 [thread overview]
Message-ID: <20070913194130.1611fd78.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070914105420.F2E9.Y-GOTO@jp.fujitsu.com>
On Fri, 14 Sep 2007 11:02:43 +0900 Yasunori Goto <y-goto@jp.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, 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:[~2007-09-14 2:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 7:25 [PATCH -mm] mm: Fix memory hotplug + sparsemem build Paul Mundt
2007-09-11 7:25 ` Paul Mundt
2007-09-11 8:18 ` Yasunori Goto
2007-09-11 8:18 ` Yasunori Goto
2007-09-11 8:25 ` Paul Mundt
2007-09-11 8:25 ` Paul Mundt
2007-09-11 9:15 ` Andy Whitcroft
2007-09-11 9:15 ` Andy Whitcroft
2007-09-11 9:37 ` Yasunori Goto
2007-09-11 9:37 ` Yasunori Goto
2007-09-14 1:44 ` Andrew Morton
2007-09-14 1:44 ` Andrew Morton
2007-09-14 2:02 ` Yasunori Goto
2007-09-14 2:02 ` Yasunori Goto
2007-09-14 2:41 ` Andrew Morton [this message]
2007-09-14 2:41 ` Andrew Morton
2007-09-14 5:14 ` Yasunori Goto
2007-09-14 5:14 ` Yasunori Goto
2007-09-14 14:09 ` Lee Schermerhorn
2007-09-14 14:09 ` Lee Schermerhorn
2007-09-14 20:51 ` Andrew Morton
2007-09-14 20:51 ` Andrew Morton
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=20070913194130.1611fd78.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.