From: Paul Jackson <pj@sgi.com>
Cc: y-goto@jp.fujitsu.com, akpm@osdl.org, apw@shadowen.org,
bob.picco@hp.com, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-ia64@vger.kernel.org,
tony.luck@intel.com, ak@suse.de, len.brown@intel.com,
discuss@x86-64.org
Subject: Re: [PATCH 001/003]Fix unify mapping from pxm to node id.
Date: Sun, 29 Jan 2006 02:38:41 -0800 [thread overview]
Message-ID: <20060129023841.439a21af.pj@sgi.com> (raw)
In-Reply-To: <20060129034434.GO7306@localhost>
Now that I applied the patches correctly:
x86-x86_64-ia64-unify-mapping-from-pxm-to-node-id.patch
x86-x86_64-ia64-unify-mapping-from-pxm-to-node-id-fix.patch
[PATCH 001/003]Fix unify mapping from pxm to node id.
[PATCH 002/003]Fix unify mapping from pxm to node id.
[PATCH 003/003]Fix unify mapping from pxm to node id.
They compiled on a 2.6.16-rc1-mm3 source base, for archs:
alpha arm i386 ia64 sparc x86_64
and they compiled and booted ok on SN2 (ia64 sn2_defconfig).
I just noticed as I typed the above that the last 3 patches all had the
same Subject "Fix unify mapping from pxm to node id." Each patch
should have a different Subject (after the [...] is stripped.)
Other than that detail ... looks good.
Acked-by: Paul Jackson <pj@sgi.com>
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
WARNING: multiple messages have this Message-ID (diff)
From: Paul Jackson <pj@sgi.com>
Cc: y-goto@jp.fujitsu.com, akpm@osdl.org, apw@shadowen.org,
bob.picco@hp.com, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-ia64@vger.kernel.org,
tony.luck@intel.com, ak@suse.de, len.brown@intel.com,
discuss@x86-64.org
Subject: Re: [PATCH 001/003]Fix unify mapping from pxm to node id.
Date: Sun, 29 Jan 2006 10:38:41 +0000 [thread overview]
Message-ID: <20060129023841.439a21af.pj@sgi.com> (raw)
In-Reply-To: <20060129034434.GO7306@localhost>
Now that I applied the patches correctly:
x86-x86_64-ia64-unify-mapping-from-pxm-to-node-id.patch
x86-x86_64-ia64-unify-mapping-from-pxm-to-node-id-fix.patch
[PATCH 001/003]Fix unify mapping from pxm to node id.
[PATCH 002/003]Fix unify mapping from pxm to node id.
[PATCH 003/003]Fix unify mapping from pxm to node id.
They compiled on a 2.6.16-rc1-mm3 source base, for archs:
alpha arm i386 ia64 sparc x86_64
and they compiled and booted ok on SN2 (ia64 sn2_defconfig).
I just noticed as I typed the above that the last 3 patches all had the
same Subject "Fix unify mapping from pxm to node id." Each patch
should have a different Subject (after the [...] is stripped.)
Other than that detail ... looks good.
Acked-by: Paul Jackson <pj@sgi.com>
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
WARNING: multiple messages have this Message-ID (diff)
From: Paul Jackson <pj@sgi.com>
To: "Bob Picco" <bob.picco@hp.com>
Cc: y-goto@jp.fujitsu.com, akpm@osdl.org, apw@shadowen.org,
bob.picco@hp.com, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-ia64@vger.kernel.org,
tony.luck@intel.com, ak@suse.de, len.brown@intel.com,
discuss@x86-64.org
Subject: Re: [PATCH 001/003]Fix unify mapping from pxm to node id.
Date: Sun, 29 Jan 2006 02:38:41 -0800 [thread overview]
Message-ID: <20060129023841.439a21af.pj@sgi.com> (raw)
In-Reply-To: <20060129034434.GO7306@localhost>
Now that I applied the patches correctly:
x86-x86_64-ia64-unify-mapping-from-pxm-to-node-id.patch
x86-x86_64-ia64-unify-mapping-from-pxm-to-node-id-fix.patch
[PATCH 001/003]Fix unify mapping from pxm to node id.
[PATCH 002/003]Fix unify mapping from pxm to node id.
[PATCH 003/003]Fix unify mapping from pxm to node id.
They compiled on a 2.6.16-rc1-mm3 source base, for archs:
alpha arm i386 ia64 sparc x86_64
and they compiled and booted ok on SN2 (ia64 sn2_defconfig).
I just noticed as I typed the above that the last 3 patches all had the
same Subject "Fix unify mapping from pxm to node id." Each patch
should have a different Subject (after the [...] is stripped.)
Other than that detail ... looks good.
Acked-by: Paul Jackson <pj@sgi.com>
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2006-01-29 10:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 11:24 [RFT/PATCH]Unify mapping from pxm to node id (take 2) Yasunori Goto
2006-01-20 11:24 ` Yasunori Goto
2006-01-23 7:57 ` Yasunori Goto
2006-01-23 7:57 ` Yasunori Goto
2006-01-26 15:48 ` Paul Jackson
2006-01-26 15:48 ` Paul Jackson
2006-01-28 3:34 ` [PATCH 001/003]Fix unify mapping from pxm to node id Yasunori Goto
2006-01-28 3:34 ` Yasunori Goto
2006-01-28 7:15 ` Paul Jackson
2006-01-28 7:15 ` Paul Jackson
2006-01-29 3:44 ` Bob Picco
2006-01-29 3:44 ` Bob Picco
2006-01-29 5:04 ` Paul Jackson
2006-01-29 5:04 ` Paul Jackson
2006-01-29 5:04 ` Paul Jackson
2006-01-29 10:38 ` Paul Jackson [this message]
2006-01-29 10:38 ` Paul Jackson
2006-01-29 10:38 ` Paul Jackson
2006-01-28 3:34 ` [PATCH 002/003]Fix " Yasunori Goto
2006-01-28 3:34 ` Yasunori Goto
2006-01-28 3:34 ` [PATCH 003/003]Fix " Yasunori Goto
2006-01-28 3:34 ` Yasunori Goto
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=20060129023841.439a21af.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=bob.picco@hp.com \
--cc=discuss@x86-64.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--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.