| 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
| ||
|
Message-ID: <20080421202919.GA28069@elte.hu> Date: Mon, 21 Apr 2008 22:29:19 +0200 From: Ingo Molnar <mingo@...e.hu> To: Adrian Bunk <bunk@...nel.org> Cc: James Bottomley <James.Bottomley@...senPartnership.com>, Alexey Starikovskiy <astarikovskiy@...e.de>, tglx@...utronix.de, hpa@...or.com, linux-kernel@...r.kernel.org Subject: Re: Voyager phys_cpu_present_map compile error * Adrian Bunk <bunk@...nel.org> wrote: > On Mon, Apr 21, 2008 at 10:13:52PM +0200, Ingo Molnar wrote: > > > > * Adrian Bunk <bunk@...nel.org> wrote: > > > > > > ok, that's good enough - that's why i excluded it from the auto-qa > > > > test-space as well. Adrian, could you please remove it from your > > > > config testset as well? If a user enables that config option it wont > > > > boot anyway so it's not a problem in practice. > > > > > > Who said that Voyager won't boot? > > > > Adrian, you build Voyager kernels so just try to boot it once on > > your PC and watch the show ... > > Ingo, an ia64 kernel also won't boot on my computer, and I'll still > compile test my patches for ia64 ... dont be silly... the ia64 kernel is not under arch/x86, it's not even the same instruction format. Voyager runs on x86 CPUs and is part of the x86 architecture tree. Ingo -- 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/
Powered by blists - more mailing lists