From: Juergen Gross <jgross@suse.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, xen-devel@lists.xensource.com,
anthony.perard@citrix.com, sstabellini@kernel.org
Subject: Re: [Qemu-devel] [PATCH 1/2] xen: add an own bus for xen backend devices
Date: Thu, 29 Sep 2016 16:39:14 +0200 [thread overview]
Message-ID: <8feedaa0-a19c-5a62-842c-297f8225adb0@suse.com> (raw)
In-Reply-To: <1474966425.26376.8.camel@redhat.com>
On 27/09/16 10:53, Gerd Hoffmann wrote:
> On Mo, 2016-09-26 at 14:43 +0200, Juergen Gross wrote:
>> Add a bus for Xen backend devices in order to be able to establish a
>> dedicated device path for pluggable devices.
>
> Looks sane to me. Can take this through the usb queue if I get an ack
> from xen.
>
>> +#define TYPE_XENSYSDEV "xensysdev"
>> +#define TYPE_XENSYSBUS "xen-sysbus"
>
> I'd make this consistent and use the dash either for both or not at all.
Okay, I'll change it to use the dash in both cases.
Juergen
next prev parent reply other threads:[~2016-09-29 14:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 12:43 [Qemu-devel] [PATCH 0/2] Xen pvUSB correction Juergen Gross
2016-09-26 12:43 ` [Qemu-devel] [PATCH 1/2] xen: add an own bus for xen backend devices Juergen Gross
2016-09-27 8:53 ` Gerd Hoffmann
2016-09-29 14:39 ` Juergen Gross [this message]
2016-09-26 12:43 ` [Qemu-devel] [PATCH 2/2] xen: add qemu device for each pvusb backend Juergen Gross
2016-09-27 9:00 ` Daniel P. Berrange
2016-09-29 14:39 ` Juergen Gross
2016-09-27 9:08 ` Gerd Hoffmann
2016-09-29 14:49 ` Juergen Gross
2016-09-29 15:16 ` Gerd Hoffmann
2016-09-29 19:39 ` Markus Armbruster
2016-09-27 8:51 ` [Qemu-devel] [PATCH 0/2] Xen pvUSB correction Gerd Hoffmann
2016-09-29 14:38 ` Juergen Gross
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=8feedaa0-a19c-5a62-842c-297f8225adb0@suse.com \
--to=jgross@suse.com \
--cc=anthony.perard@citrix.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).