From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Date: Wed, 10 Oct 2018 16:38:47 +0000
Subject: Re: [GIT PULL] Please pull my kvm-ppc-next-4.20-1 tag
Message-Id: <360cd9cc-4566-a3f1-27da-d2950ee310d1@redhat.com>
List-Id: <kvm-ppc.vger.kernel.org>
References: <20180119044850.GA10633@fergus.ozlabs.ibm.com>
In-Reply-To: <20180119044850.GA10633@fergus.ozlabs.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: kvm-ppc@vger.kernel.org

On 10/10/2018 07:55, Paul Mackerras wrote:
> 
> Stephen Rothwell noted that there is a conflict between my
> kvm-ppc-next tree and the kvm-arm tree, in that we have both allocated
> the next free capability number (160).  It would be nice to get a
> stable allocation for the new capability that I need (one which
> reports/enables nested virtualization support for the HV KVM module)
> so that the necessary QEMU patches can be submitted.

Since you sent the pull request first, you get to use 160. :)

Paolo