linux-kernel - Re: [GIT PULL] KVM updates for the 3.4 merge window

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]

Message-ID: <20120326213809.GA29788@bloggs.ozlabs.ibm.com>
Date:	Tue, 27 Mar 2012 08:38:09 +1100
From:	Paul Mackerras <paulus@...ba.org>
To:	Avi Kivity <avi@...hat.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	KVM list <kvm@...r.kernel.org>,
	Marcelo Tosatti <mtosatti@...hat.com>,
	Paul Mackerras <paulus@....ibm.com>,
	Alexander Graf <agraf@...e.de>
Subject: Re: [GIT PULL] KVM updates for the 3.4 merge window

On Sun, Mar 25, 2012 at 12:09:05PM +0200, Avi Kivity wrote:

> I can switch to fast-forward-only in the future, but I'm afraid that
> this particular tree is broken for good.  The un-rebased
> fast-forward-only source for this is kvm.git master, which I don't think
> you want to pull.  It will cause every kvm commit to appear twice and
> confuse everyone.

There are patches from me in there that have been pending since
December last year, and now look like they won't be going upstream
until June.  So, under the circumstances, how would you (Avi) feel
about Ben and I committing the KVM patches that only affect powerpc to
Ben's tree and sending them to Linus that way before the merge window
closes?

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