From: keith mannthey <kmannth@us.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: andrew <akpm@osdl.org>,
y-goto@jp.fujitsu.com, lkml <linux-kernel@vger.kernel.org>,
lhms-devel <lhms-devel@lists.sourceforge.net>
Subject: Re: [PATCH] memory hotadd fixes [6/5] enhance collistion check
Date: Fri, 04 Aug 2006 14:01:16 -0700 [thread overview]
Message-ID: <1154725276.5784.1.camel@keithlap> (raw)
In-Reply-To: <20060804113245.30487789.kamezawa.hiroyu@jp.fujitsu.com>
On Fri, 2006-08-04 at 11:32 +0900, KAMEZAWA Hiroyuki wrote:
> Okay... here is 6/5 patch..
>
> On Fri, 4 Aug 2006 11:15:50 +0900
> KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > > > Maybe moving ioresouce collision check in early stage of add_memory() is good ?
> > > Yea. I am working a a full patch set for but my sparsemem and reserve
> > > add-based paths. It creates a valid_memory_add_range call at the start
> > > of add_memory. I should be posting the set in the next few hours.
> > >
> > Ah..ok. but I wrote my own patch...and testing it now..
> >
>
> This patch passed test with ia64. based on 5 patches already sent.
> plz check.
Looks good to me. Tested as works x86_64. It is required for the 4th
patch of this series.
Acked-by: Keith Mannthey <kmannth@us.ibm.com>
next prev parent reply other threads:[~2006-08-04 21:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 3:36 [PATCH] memory hotadd fixes [4/5] avoid check in acpi KAMEZAWA Hiroyuki
2006-08-03 18:28 ` keith mannthey
2006-08-03 23:09 ` [Lhms-devel] " keith mannthey
2006-08-04 0:22 ` KAMEZAWA Hiroyuki
2006-08-04 0:13 ` keith mannthey
2006-08-04 0:44 ` KAMEZAWA Hiroyuki
2006-08-04 1:54 ` keith mannthey
2006-08-04 2:15 ` KAMEZAWA Hiroyuki
2006-08-04 2:32 ` [PATCH] memory hotadd fixes [6/5] enhance collistion check KAMEZAWA Hiroyuki
2006-08-04 3:09 ` keith mannthey
2006-08-04 3:19 ` KAMEZAWA Hiroyuki
2006-08-04 21:01 ` keith mannthey [this message]
2006-08-04 3:00 ` [PATCH] memory hotadd fixes [4/5] avoid check in acpi keith mannthey
2006-08-04 3:13 ` KAMEZAWA Hiroyuki
2006-08-04 3:23 ` keith mannthey
2006-08-04 3:48 ` KAMEZAWA Hiroyuki
2006-08-04 4:25 ` keith mannthey
2006-08-04 4:32 ` KAMEZAWA Hiroyuki
2006-08-04 8:23 ` Mika Penttilä
2006-08-04 8:32 ` keith mannthey
2006-08-04 5:46 ` Yasunori Goto
2006-08-04 5:59 ` [Lhms-devel] " KAMEZAWA Hiroyuki
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=1154725276.5784.1.camel@keithlap \
--to=kmannth@us.ibm.com \
--cc=akpm@osdl.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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