[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191217175507.GA8052@linux.intel.com>
Date: Tue, 17 Dec 2019 09:55:08 -0800
From: Sean Christopherson <sean.j.christopherson@...el.com>
To: Christian Borntraeger <borntraeger@...ibm.com>
Cc: James Hogan <jhogan@...nel.org>,
Paul Mackerras <paulus@...abs.org>,
Janosch Frank <frankja@...ux.ibm.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Radim Krčmář <rkrcmar@...hat.com>,
Marc Zyngier <maz@...nel.org>,
David Hildenbrand <david@...hat.com>,
Cornelia Huck <cohuck@...hat.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>,
James Morse <james.morse@....com>,
Julien Thierry <julien.thierry.kdev@...il.com>,
Suzuki K Poulose <suzuki.poulose@....com>,
linux-mips@...r.kernel.org, kvm-ppc@...r.kernel.org,
kvm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
kvmarm@...ts.cs.columbia.edu, linux-kernel@...r.kernel.org,
Christoffer Dall <christoffer.dall@....com>
Subject: Re: [PATCH v3 00/15] KVM: Dynamically size memslot arrays
On Mon, Dec 16, 2019 at 09:25:24AM +0100, Christian Borntraeger wrote:
>
> On 13.12.19 21:01, Sean Christopherson wrote:
> > Applies cleanly on the current kvm/queue and nothing caught fire in
> > testing (though I only re-tested the series as a whole).
>
> Do you have the latest version somewhere on a branch? The version on the
> list no longer applies cleanly.
Ah, I only tested with my sparse x86-only tree. The result with three-way
merging, i.e. 'git am -3', looks correct at a glance.
Regardless, I need to spin a new version to handle a conflict with an
unrelated in-flight memslots bug fix, I'll get that sent out today.
Powered by blists - more mailing lists