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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20120330120107.GA28503@bloggs.ozlabs.ibm.com>
Date:	Fri, 30 Mar 2012 23:01:07 +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 Tue, Mar 27, 2012 at 12:09:44PM +0200, Avi Kivity wrote:

> > 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?
> 
> That's fine if there are no interdependencies.  It looks like 74df956
> will be a problem though.
> 
> The other two options are:
> 
> - I'll add my signoff to the commits that lack it.  This unbreaks the
> committer lacks signoff.

I just noticed that the branch you asked Linus to pull includes none
of the patches that Alex sent you in the last batch, in the email with
subject "[PULL 00/56] ppc patch queue 2012-03-15" sent on March 15,
where he asked you to pull git://github.com/agraf/linux-2.6.git
for-upstream.

What happened?  Did they get lost in the re-signing, or is there some
reason you thought they shouldn't go in?

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