linux-kernel - Re: x86 setup rewrite tree ready for flamage^W review

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]

Message-ID: <46417215.6060204@zytor.com>
Date:	Wed, 09 May 2007 00:02:45 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Sam Ravnborg <sam@...nborg.org>
CC:	"Antonino A. Daplas" <adaplas@...il.com>, Andi Kleen <ak@...e.de>,
	Andrew Morton <akpm@...l.org>,
	Matt Domsch <Matt_Domsch@...l.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Vivek Goyal <vgoyal@...ibm.com>,
	James Bottomley <James.Bottomley@...senPartnership.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: x86 setup rewrite tree ready for flamage^W review

Sam Ravnborg wrote:
>> http://www.kernel.org/pub/linux/kernel/people/hpa/newsetup-36f021b5.patch
> 
> Are you planning to rebase to -linus and then let
> arch/x86_64/boot/Makefile be a reference to i386/boot/Makefile?
> 
> The patch for kbuild to enable this is in -linus now.
> 
> As for the important part (the code) I have not looked.

I have rebased to -linus, but I'm a bit scared about making that
particular change at this time, mostly because it requires some
additional Makefile work which I would be happier to apply later, in
order to make the "create clean patchset" task easier.

All the source code is shared, but for right now the Makefiles are
slightly different, mostly w.r.t. CFLAGS.

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