From: Andy Whitcroft <apw@shadowen.org>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: Andrew Morton <akpm@osdl.org>, "Luck, Tony" <tony.luck@intel.com>,
Andi Kleen <ak@suse.de>, "Brown, Len" <len.brown@intel.com>,
Bob Picco <bob.picco@hp.com>, Paul Jackson <pj@sgi.com>,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
ACPI-ML <linux-acpi@vger.kernel.org>,
linux-ia64@vger.kernel.org, x86-64 Discuss <discuss@x86-64.org>
Subject: Re: [Patch:000/004] Unify pxm_to_node id ver.2.
Date: Wed, 01 Feb 2006 14:35:25 +0000 [thread overview]
Message-ID: <43E0C72D.4070709@shadowen.org> (raw)
In-Reply-To: <20060201205152.41E6.Y-GOTO@jp.fujitsu.com>
Yasunori Goto wrote:
> Hello.
>
> I rewrote patches to unify mapping from pxm to node id as ver.2.
> I already posted all of fixes for ver.1.
> However, searching first patch and appling fixes are a bit messy
> due to too many mail and patches in LKML.
> So, I rearranged them to find all of them easier.
> Basically, (ver.1 + previous fix patches) = ver.2.
> But ver.2 is set of following patches.
> - generic code.
> - for ia64.
> - for x86_64.
> - for i386.
>
> Fixes from ver.1 are followigs.
> - They are for 2.6.16-rc1-mm4.
> - Fix old map from HP and SGI's code by Bob Picco-san.
> - Remove MAX_PXM_DOMAINS from asm-ia64/acpi.h. It is already defined at
> include/acpi/acpi_numa.h.
> - Fix return code of setup_node() at arch/x86_64/mm/srat.c
> - Fix ACPI_NUMA config for i386 by Andy Witcroft-san.
> - Define dummy functions for i386's compile error.
> - Remove garbage nid_to_pxm_map from acpi20_parse_srat()
> at arch/i386/kernel/srat.c
>
> I tested ia64 and x86_64 with dummy SRAT NUMA emulation.
> And I checked compile completion for hp, SGI, and Summit.
Ran it across my test boxes, builds and boots on the affected platforms
and generally elsewhere.
-apw
prev parent reply other threads:[~2006-02-01 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 12:36 [Patch:000/004] Unify pxm_to_node id ver.2 Yasunori Goto
2006-02-01 14:35 ` Andy Whitcroft [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=43E0C72D.4070709@shadowen.org \
--to=apw@shadowen.org \
--cc=ak@suse.de \
--cc=akpm@osdl.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=pj@sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox