linux-kernel - Re: [PATCH 0/2] x86/pci: Renaming numa into numaq

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] [day] [month] [year] [list]

Date:	Fri, 11 Jul 2008 14:24:20 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Robert Richter <robert.richter@....com>,
	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] x86/pci: Renaming numa into numaq

On Friday, July 11, 2008 12:27:33 pm Ingo Molnar wrote:
> * Robert Richter <robert.richter@....com> wrote:
> > This patch series renames numa into numaq for x86/pci code.
>
> applied to tip/x86/unify-pci:
>
>   Robert Richter (5):
>        x86/pci: Removing pci-y in Makefile
>        x86/pci: Changing subsystem initialization order for NUMA
>        x86/pci: renamed: numa.c -> numaq_32.c
>        x86/pci: renaming numa into numaq
>        x86/pci: Changing subsystem init for visws
>
> thanks Robert.
>
> Jesse, do you give us a general Ack for this direction and these
> commits? The changes are way too intermixed with other x86 bits to be
> cleanly separable at this stage, so it would be nice if we merged this
> via the x86 tree. Find below a list of commit IDs that change
> arch/x86/pci/ - all but the last few ones are in linux-next as well.

Yeah, no problem with the general direction.  I'll re-review Robert's latest 
stuff when I get a chance, but it looked pretty good to me in the first pass.

Thanks,
Jesse
--
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/