linux-kernel - Re: x86/non-x86: percpu, node ids, apic ids x86.git fixup

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:	Wed, 30 Jan 2008 13:13:02 -0600
From:	Olof Johansson <olof@...om.net>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	"Luck, Tony" <tony.luck@...el.com>, sparclinux@...r.kernel.org,
	linux-ia64@...r.kernel.org,
	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	Mike Travis <travis@....com>,
	Linux/PPC Development <linuxppc-dev@...abs.org>,
	Geert Uytterhoeven <Geert.Uytterhoeven@...ycom.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: x86/non-x86: percpu, node ids, apic ids x86.git fixup

On Wed, Jan 30, 2008 at 07:49:20PM +0100, Ingo Molnar wrote:
> 
> * Luck, Tony <tony.luck@...el.com> wrote:
> 
> > > Could you check the patch below? With this applied to latest -git, 
> > > ia64 buils fine for me in a cross-compiling environment. (but i dont 
> > > know whether it boots ...)
> > 
> > Uni-processor build still fails with this patch (config is 
> > arch/ia64/configs/tiger_defconfig with CONFIG_SMP switched from =y to 
> > =n).
> 
> could you try the full patchset that Travis has just sent and which i've 
> put into x86.git, you can pull it from:

Looks ok for powerpc so far, I haven't gotten through all defconfigs yet
but the first ones that failed before build now. pasemi_defconfig boots
as well.


-Olof
--
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/