From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56663)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <amit.shah@redhat.com>) id 1aZAvk-00081g-KL
	for qemu-devel@nongnu.org; Fri, 26 Feb 2016 00:27:09 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <amit.shah@redhat.com>) id 1aZAvh-0005YW-FT
	for qemu-devel@nongnu.org; Fri, 26 Feb 2016 00:27:08 -0500
Received: from mx1.redhat.com ([209.132.183.28]:44074)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <amit.shah@redhat.com>) id 1aZAvh-0005YS-AE
	for qemu-devel@nongnu.org; Fri, 26 Feb 2016 00:27:05 -0500
Date: Fri, 26 Feb 2016 10:57:00 +0530
From: Amit Shah <amit.shah@redhat.com>
Message-ID: <20160226052700.GN10967@grmbl.mre>
References: <20160115092419.GA2432@work-vm>
	<1453408767-4905-1-git-send-email-silbe@linux.vnet.ibm.com>
	<20160225050552.GL10967@grmbl.mre>
	<871t80bkqw.fsf@oc4731375738.ibm.com>
	<87y4a8a598.fsf@oc4731375738.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87y4a8a598.fsf@oc4731375738.ibm.com>
Subject: Re: [Qemu-devel] [PATCH qemu] migration/vmstate: document
	VMStateFlags
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Sascha Silbe <silbe@linux.vnet.ibm.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org, "Dr. David Alan Gilbert" <dgilbert@redhat.com>, Juan Quintela <quintela@redhat.com>

On (Thu) 25 Feb 2016 [21:45:23], Sascha Silbe wrote:
> Dear Amit,
> 
> > Amit Shah <amit.shah@redhat.com> writes:
> >
> >> On (Thu) 21 Jan 2016 [21:39:27], Sascha Silbe wrote:
> >>> The VMState API is rather sparsely documented. Start by describing the
> >>> meaning of all VMStateFlags.
> >
> >> Thanks, I've pulled this in my queue.
> >>
> >> There's one new flag added: VMS_MULTIPLY_ELEMENTS.  Do you want to
> >> send a follow-up patch to add a description to that one as well?
> >
> > I can either send a new version with the conflicts resolved and
> > VMS_MULTIPLY_ELEMENTS documented (i.e. rebased on current master), or a
> > follow-up patch with just the differences to your version if you point
> > me at your git repo. Whatever works best for you.
> 
> FWIW, here's the version based on current master. As mentioned before;
> I'm happy to rebase on your version if you prefer.

Thanks, can you please post this as a standalone email?  Easier for me
to apply.

Thanks,

		Amit