From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Date: Tue, 25 Mar 2014 17:29:45 +0000
Subject: Preparing kvm/next for first pull request of 3.15 merge window
Message-Id: <5331BD09.6090806@redhat.com>
List-Id: <kvm-ppc.vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>, kvm-ppc <kvm-ppc@vger.kernel.org>, Marc Zyngier <marc.zyngier@arm.com>, Christoffer Dall <christoffer.dall@linaro.org>, Alexander Graf <agraf@suse.de>, Scott Wood <scottwood@freescale.com>, Paul Mackerras <paulus@samba.org>

Hi all,

I've pushed the last set of updates to kvm/next for the 3.15 merge 
window.  I don't expect any other changes for either x86 or s390 (thanks 
Christian!).  The pull request is already pretty beefy.

I would like to know from ARM and PPC maintainers *now* (before the 
merge window opens) what will be in 3.15.  Also, PPC guys, please make 
sure the pull requests will be based on commit e724f080f5dd (KVM: PPC: 
Book3S HV: Fix register usage when loading/saving VRSAVE, 2014-03-13).

Also, the pull requests I got in the last couple of months were a bit 
messy, and I'm already fearing that Linus notices.  In the future, I'll 
tag kvm-3.x-base (e.g. kvm-3.16-base) when I open kvm/next, and I will 
*reject* pull requests from submaintainers that include extra non-KVM 
commits without a very good reason.

Palo