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]
Message-ID: <10234.1326729002@redhat.com>
Date:	Mon, 16 Jan 2012 15:50:02 +0000
From:	David Howells <dhowells@...hat.com>
To:	torvalds@...ux-foundation.org
Cc:	dhowells@...hat.com, arnd@...db.de, alan@...rguk.ukuu.org.uk,
	hpa@...or.com, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org, airlied@...hat.com
Subject: Pulling the rest of the User-API header split patches


Hi Linus,

Thanks for pulling the User-API header split preliminary patches.

Will you be pulling the rest of the patches to actually perform the split at
the end of this merge window?  If so, as previously mentioned, I'll need to
regenerate them before you do.

However, for the moment, I dropped the preliminary patches from my tree and
regenerated the rest based on the tree I saw this morning:

http://git.infradead.org/users/dhowells/linux-headers.git/shortlog/refs/heads/uapi-split

I've made 'make allyesconfig' build again on x86_64.  arch/x86/lib/insn.c is
compiled for use in both userspace and kernelspace, necessitating a bit of
#include adjustment, but that was the only necessary change.  I've also had
Dave Airlie review the preparatory DRM patches and those have been adjusted.

An opinion, if I may: I have been checking the scripts into the GIT tree (with
the intention to delete them later) so that a record of them is retained - but
I wonder if I should bother...  Hopefully, once the scripts are run and the
results applied, it won't be necessary to retain the scripts.

Thanks,
David
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ