linux-kernel - Re: linux-next: fate of the kvmtool tree

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 3 Oct 2012 09:47:34 +0300
From:	Pekka Enberg <penberg@...nel.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Sasha Levin <levinsasha928@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Linus <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: linux-next: fate of the kvmtool tree

Hi Stephen,

On Wed, Oct 3, 2012 at 8:29 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Well, here we are at another merge window and the kvmtool tree is still
> not merged.  So, is it likely that it will be merged in this merge
> window?  or the next?  If not, can I please remove it from linux-next
> (and have it removed from the auto-latest branch of the tip tree) as it
> just adds weight to the patches and the tree that people have to fetch to
> work with.

I have no idea how likely it is that it will be merged but I'm
planning to send a pull request for this merge cycle. ;-)

Btw, IIRC the KVM tool also ends up in linux-next via Ingo's tree so
dropping my tree might not be enough.

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