From mboxrd@z Thu Jan  1 00:00:00 1970
From: Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH 0/3] KVM_VCPU_GET_REG_LIST API
Date: Fri, 19 Oct 2012 16:49:37 +1030
Message-ID: <87vce72dc6.fsf@rustcorp.com.au>
References: <1346831926-31820-1-git-send-email-rusty.russell@linaro.org> <5080161C.9080209@redhat.com> <87objzpabx.fsf@rustcorp.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm@vger.kernel.org,
	Christoffer Dall <c.dall@virtualopensystems.com>,
	Alexander Graf <agraf@suse.de>,
	Peter Maydell <peter.maydell@linaro.org>
To: Avi Kivity <avi@redhat.com>,
	Rusty Russell <rusty.russell@linaro.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from ozlabs.org ([203.10.76.45]:48522 "EHLO ozlabs.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753234Ab2JSGYs (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 19 Oct 2012 02:24:48 -0400
In-Reply-To: <87objzpabx.fsf@rustcorp.com.au>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Rusty Russell <rusty@rustcorp.com.au> writes:
> Avi Kivity <avi@redhat.com> writes:
>> On 09/05/2012 10:58 AM, Rusty Russell wrote:
>>> This is the generic part of the KVM_SET_ONE_REG/KVM_GET_ONE_REG
>>> enhancements which ARM wants, rebased onto kvm/next.
>>
>> This was stalled for so long it needs rebasing again, sorry.
>>
>> But otherwise I'm happy to apply.
>
> Ok, will rebase and re-test against kvm-next.

Wait, what?  kvm/arm isn't in kvm-next?

This will produce a needless clash with that, which is more important
than this cleanup.  I'll rebase this as soon as that is merged.

Christoffer, is there anything I can help with?

Cheers,
Rusty.