linux-kernel - Re: [BUGFIX][PATCH] cpu to node relationship fixup take2 [1/2] acpi_map

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 22 Sep 2006 17:06:04 -0700
From:	Andrew Morton <akpm@...l.org>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	"tony.luck@...el.com" <tony.luck@...el.com>,
	"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>, GOTO <y-goto@...fujitsu.com>
Subject: Re: [BUGFIX][PATCH] cpu to node relationship fixup take2 [1/2]
 acpi_map_cpu2node

On Fri, 22 Sep 2006 15:24:47 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> wrote:

> I rewrote the whoe patch..
> 

Well I don't recall ever having seen a "cpu to node relationship fixup
take1" and I have generally lost the plot regarding these fixes.

What I have now is:

cpu-to-node-relationship-fixup-take2.patch
cpu-to-node-relationship-fixup-map-cpu-to-node.patch

I shall send those patches in reply to this email.  Please confirm that
these are correct, sufficient, complete, etc.

Do you believe these are needed in 2.6.18.x?

Please follow the guidelines in
http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt a little more
closely, especially regarding Subject:s

Please bear in mind that I'm sitting on thousands of patches from hundreds
of developers, that I process sometimes hundreds of patches per day and I
am very easily confused.  Retaining consistent and well-thought out
Subject:s and referring to previous patches via their precise Subject:s
really helps, 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/