From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH 0/4] KVM: Introduce kvm_memory_slot::arch
Date: Tue, 7 Feb 2012 15:42:45 -0200
Message-ID: <20120207174245.GA18767@amt.cnet>
References: <20120130124859.6c3bb19f.yoshikawa.takuya@oss.ntt.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: avi@redhat.com, kvm@vger.kernel.org
To: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:40416 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754563Ab2BGRom (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 7 Feb 2012 12:44:42 -0500
Content-Disposition: inline
In-Reply-To: <20120130124859.6c3bb19f.yoshikawa.takuya@oss.ntt.co.jp>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Mon, Jan 30, 2012 at 12:48:59PM +0900, Takuya Yoshikawa wrote:
> This is the first step to separate the architecture specific members.
> The rmap and dirty_bitmap can be treated later based on this.
> 
> v1->v2:
> 
>   Patch 3:
>   - Removed extra checks for NULL when we create a new slot.
>   - Removed "if (user_alloc)" check taken from the s390 code.
> 
>   Patch 4:
>   - Just rebased.

Patch 3 does not apply, please rebase and resend whole series.