From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH 27/27] tools/libxl: Drop all knowledge of
 toolstack callbacks
Date: Wed, 17 Jun 2015 11:14:16 +0100
Message-ID: <1434536056.13744.298.camel@citrix.com>
References: <1434375880-30914-1-git-send-email-andrew.cooper3@citrix.com>
	<1434375880-30914-28-git-send-email-andrew.cooper3@citrix.com>
	<1434467058.13744.214.camel@citrix.com> <55803B79.2080707@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <55803B79.2080707@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Yang Hongyang <yanghy@cn.fujitsu.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, Xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

On Tue, 2015-06-16 at 16:06 +0100, Andrew Cooper wrote:
> On 16/06/15 16:04, Ian Campbell wrote:
> > On Mon, 2015-06-15 at 14:44 +0100, Andrew Cooper wrote:
> >> Libxl has now been fully adjusted not to need them.
> >>
> >> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> > Acked-by: Ian Campbell <Ian.Campbell@citrix.com>
> >
> > /me looks mournfully at the #28 shaped hole in this series which would
> > nuke all the migration v1 code from libxc :-)
> 
> I was going to slip that into v2.  I didn't want to delay posting v1 for
> review, given the proximity of the 4.6 freeze.
> 
> I think I will transcribe the description of the legacy protocol from
> xg_save_restore.h

That would be good, thanks.

>  and code up the legacy protocol in python.

That would be above and beyond, but don't let me stop you ;-)

Ian.