linux-kernel - Re: kvmtool (Was: Re: Linux 3.2-rc2)

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: <CAOJsxLFQk0kzmjnr0ds1-JJy3KBdGu-txsb06Na0kPg5LZA3vg@mail.gmail.com>
Date:	Wed, 16 Nov 2011 08:34:58 +0200
From:	Pekka Enberg <penberg@...nel.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Sasha Levin <levinsasha928@...il.com>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: kvmtool (Was: Re: Linux 3.2-rc2)

On Wed, Nov 16, 2011 at 5:36 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> That is true (see http://neuling.org/linux-next-size.html).  However,
> linux-next "bottomed out" with >1500 (non-merge) commits still in it.  Of
> those, 900 are from the kvmtool tree,  So, has there been any decision
> about whether kvmtool will ever be included in the upstream tree?
>
> I do not want to reinflame the discussion and am happy to carry it along
> (it doesn't really interact with the rest of the tree), but if it is
> never going to be merged, then I may as well drop it.

There hasn't been a decision either way and we will certainly try
again in the next merge window. I think it's best to keep it in
linux-next.

                        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/