linux-kernel - Re: [PATCH 0/39] Merge files at x86/lib

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: <48686AD3.1070300@kernel.org>
Date:	Sun, 29 Jun 2008 22:10:43 -0700
From:	"H. Peter Anvin" <hpa@...nel.org>
To:	Glauber Costa <gcosta@...hat.com>
CC:	linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...e.hu,
	x86@...nel.org
Subject: Re: [PATCH 0/39] Merge files at x86/lib

Glauber Costa wrote:
> Hey folks,
> 
> Here it goes a series of patch that merges some user-related files.
> From x86/lib, delay.c, getuser.S, and putuser.S are merged. For the
> last two of them, the accompanying include/asm-x86/uaccess.h is merged.
> Or close to. There are some small leftovers, that are sufficiently
> different to remain in its own files.
> 
> As for bisectability, all patches have been tested in more than 20
> different configs for both i386 and x86_64, in the usual way (just
> I'm testing in more configs now). If you find a build bug in this
> series, please send me the offending config so I can add to my poll.
> 
> The diffstat and the one-big-patch follows at the end of this introductory
> message.
> 
> Ingo, in the absence of any objections, you can pull this work from:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/glommer/linux-2.6-x86-integration.git master
> 
> into your tip/master tree
> 

Hi Glauber,

Applied to -tip as x86/unify-lib.

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