From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sean Christopherson Date: Tue, 17 Dec 2019 17:55:08 +0000 Subject: Re: [PATCH v3 00/15] KVM: Dynamically size memslot arrays Message-Id: <20191217175507.GA8052@linux.intel.com> List-Id: References: <20191024230744.14543-1-sean.j.christopherson@intel.com> <20191203221433.GK19877@linux.intel.com> <20191213200151.GF31552@linux.intel.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Christian Borntraeger Cc: James Hogan , Paul Mackerras , Janosch Frank , Paolo Bonzini , Radim =?utf-8?B?S3LEjW3DocWZ?= , Marc Zyngier , David Hildenbrand , Cornelia Huck , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , James Morse , Julien Thierry , Suzuki K Poulose , linux-mips@vger.kernel.org, kvm-ppc@vger.kernel.org, kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org, Christoffer Dall 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.