From: George Dunlap <george.dunlap@eu.citrix.com>
To: Olaf Hering <olaf@aepfle.de>, xen-devel@lists.xen.org
Cc: ian.jackson@citrix.com, wei.liu2@citrix.com,
ian.campbell@citrix.com, Chunyan Liu <cyliu@suse.com>
Subject: Re: [PATCH V3 1/6] libxl: export some functions for pvusb use
Date: Mon, 18 May 2015 14:34:19 +0100 [thread overview]
Message-ID: <5559EA5B.5000103@eu.citrix.com> (raw)
In-Reply-To: <20150420162505.GA31885@aepfle.de>
On 04/20/2015 05:25 PM, Olaf Hering wrote:
> On Sun, Apr 19, Chunyan Liu wrote:
>
>> +++ b/tools/libxl/libxl_internal.h
>
>> +_hidden int libxl__device_nextid(libxl__gc *gc, uint32_t domid, char *device);
>> +_hidden int libxl__resolve_domid(libxl__gc *gc, const char *name,
>> + uint32_t *domid);
>
>> +/* generic callback for devices that only need to set ao_complete */
>> +_hidden void device_addrm_aocomplete(libxl__egc *egc, libxl__ao_device *aodev);
>
> If that goes in I may move some or all of the vscsi code in libxl.c into
> libxl_vscsi.c.
It sounds like this would be useful independent of the pvusb stuff.
-George
next prev parent reply other threads:[~2015-05-18 13:34 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 3:50 [PATCH V3 0/6] libxl pvusb toolstack work Chunyan Liu
2015-04-19 3:50 ` [PATCH V3 1/6] libxl: export some functions for pvusb use Chunyan Liu
2015-04-20 16:25 ` Olaf Hering
2015-05-18 13:34 ` George Dunlap [this message]
2015-05-18 14:05 ` Wei Liu
2015-04-19 3:50 ` [PATCH V3 2/6] libxl_read_file_contents: fix reading sysfs file Chunyan Liu
2015-05-18 14:23 ` Ian Jackson
2015-05-18 14:28 ` Ian Campbell
2015-05-18 14:30 ` Wei Liu
2015-05-19 3:21 ` Chun Yan Liu
2015-05-18 14:25 ` Wei Liu
2015-04-19 3:50 ` [PATCH V3 3/6] libxl: add pvusb API Chunyan Liu
2015-04-20 5:53 ` Juergen Gross
2015-05-18 13:55 ` Olaf Hering
2015-05-18 18:07 ` Wei Liu
2015-05-19 3:20 ` Chun Yan Liu
2015-05-19 10:20 ` George Dunlap
2015-05-19 11:31 ` Jürgen Groß
2015-05-20 9:04 ` Wei Liu
2015-05-20 9:12 ` Ian Campbell
2015-05-20 9:30 ` Chun Yan Liu
2015-06-11 16:54 ` Ian Jackson
2015-05-19 18:06 ` George Dunlap
2015-05-19 18:24 ` Ian Campbell
2015-06-08 9:06 ` 答复: " Chun Yan Liu
2015-05-19 18:16 ` George Dunlap
2015-06-08 11:15 ` 答复: " Chun Yan Liu
2015-05-19 18:20 ` George Dunlap
2015-04-19 3:50 ` [PATCH V3 4/6] xl: add pvusb commands Chunyan Liu
2015-04-20 8:12 ` Juergen Gross
2015-04-21 2:21 ` Chun Yan Liu
2015-05-20 14:20 ` George Dunlap
2015-05-20 14:33 ` Juergen Gross
2015-05-20 14:41 ` George Dunlap
2015-05-20 14:55 ` Juergen Gross
2015-05-20 15:25 ` George Dunlap
2015-05-21 3:35 ` Juergen Gross
2015-05-21 10:37 ` George Dunlap
2015-05-21 10:52 ` Juergen Gross
2015-05-21 11:11 ` George Dunlap
2015-05-21 11:58 ` Juergen Gross
2015-05-21 13:01 ` George Dunlap
2015-05-21 13:08 ` Juergen Gross
2015-05-21 13:43 ` George Dunlap
2015-05-21 13:55 ` Juergen Gross
2015-05-21 14:00 ` George Dunlap
2015-05-21 14:14 ` Juergen Gross
2015-05-20 14:23 ` George Dunlap
2015-05-20 15:46 ` George Dunlap
2015-05-20 15:55 ` George Dunlap
2015-04-19 3:50 ` [PATCH V3 5/6] domcreate: support pvusb in configuration file Chunyan Liu
2015-04-19 3:50 ` [PATCH V3 6/6] refactor codes to unify pvusb and qemu emulated usb Chunyan Liu
2015-05-21 14:17 ` George Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5559EA5B.5000103@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=cyliu@suse.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=olaf@aepfle.de \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.