From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH v5 3/5] libxl: add support for vscsi
Date: Fri, 15 May 2015 10:48:23 +0100
Message-ID: <1431683303.8943.53.camel@citrix.com>
References: <1430918892-20928-1-git-send-email-olaf@aepfle.de>
	<1430918892-20928-4-git-send-email-olaf@aepfle.de>
	<1431528246.8263.307.camel@citrix.com>
	<1431529969.8263.324.camel@citrix.com>
	<20150513173116.GA24093@aepfle.de>
	<555571DD.5050702@suse.com> <20150515055859.GA18533@aepfle.de>
	<1431679659.8943.4.camel@citrix.com> <5555BDCF.1050001@suse.com>
	<1431683210.8943.51.camel@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: <1431683210.8943.51.camel@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: Juergen Gross <jgross@suse.com>
Cc: Olaf Hering <olaf@aepfle.de>, Wei Liu <wei.liu2@citrix.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, George Dunlap <george.dunlap@eu.citrix.com>, Ian Jackson <ian.jackson@eu.citrix.com>, Chunyan Liu <cyliu@suse.com>, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

On Fri, 2015-05-15 at 10:46 +0100, Ian Campbell wrote:
> I'd like to start with seeing an expanded version of the comment in
> libxl.h which begins:
> 
> /*
>  * Devices
>  * =======
> 
> which covers this new style API alongside the existing one and sets out
> the expected pattern of naming (both struct and function) in the same
> way.

Which would need to be agreed with the PVUSB series author(s) too. In
fact I think they may already incorporate such an API proposal (even if
only implicitly). The first step should probably be to see if that API
can be generalised to apply to pvsci first, and then hopefully write
down the generalised form.

Ian