From: Greg KH <gregkh@linuxfoundation.org>
To: Juergen Gross <jgross@suse.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
konrad.wilk@oracle.com, david.vrabel@citrix.com,
boris.ostrovsky@oracle.com, linux-usb@vger.kernel.org
Subject: Re: [Patch V4 1/3] usb: Add Xen pvUSB protocol description
Date: Wed, 22 Jul 2015 16:46:40 -0700 [thread overview]
Message-ID: <20150722234640.GA29425@kroah.com> (raw)
In-Reply-To: <1435042405-14235-2-git-send-email-jgross@suse.com>
On Tue, Jun 23, 2015 at 08:53:23AM +0200, Juergen Gross wrote:
> Add the definition of pvUSB protocol used between the pvUSB frontend in
> a Xen domU and the pvUSB backend in a Xen driver domain (usually Dom0).
>
> This header was originally provided by Fujitsu for Xen based on Linux
> 2.6.18.
>
> Changes are:
> - adapt to Linux style guide
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> include/xen/interface/io/usbif.h | 252 +++++++++++++++++++++++++++++++++++++++
Why is this a different interface than the existing ones we have today
(i.e. usbip?) Where is it documented? Do the Xen developers /
maintainers agree with this interface and code? I need their sign-off
before I can accept such a thing.
thanks,
greg k-h
next prev parent reply other threads:[~2015-07-22 23:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 6:53 [Patch V4 0/3] xen, usb: support pvUSB frontend driver Juergen Gross
[not found] ` <1435042405-14235-1-git-send-email-jgross-IBi9RG/b67k@public.gmane.org>
2015-06-23 6:53 ` [Patch V4 1/3] usb: Add Xen pvUSB protocol description Juergen Gross
2015-07-22 23:46 ` Greg KH [this message]
2015-07-23 4:04 ` Juergen Gross
[not found] ` <55B067D7.3030904-IBi9RG/b67k@public.gmane.org>
2015-07-23 4:36 ` Greg KH
[not found] ` <20150723043653.GA31524-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-07-23 6:46 ` Juergen Gross
[not found] ` <55B08DB9.60902-IBi9RG/b67k@public.gmane.org>
2015-07-23 9:38 ` [Xen-devel] " David Vrabel
2015-07-23 19:08 ` Greg KH
2015-07-23 21:29 ` Pasi Kärkkäinen
2015-07-24 3:51 ` Juergen Gross
[not found] ` <55B1B628.7090200-IBi9RG/b67k@public.gmane.org>
2015-07-24 18:57 ` Greg KH
2015-07-24 19:25 ` Konrad Rzeszutek Wilk
[not found] ` <1435042405-14235-2-git-send-email-jgross-IBi9RG/b67k@public.gmane.org>
2015-07-23 9:39 ` [Xen-devel] " David Vrabel
2015-06-23 6:53 ` [Patch V4 2/3] usb: Introduce Xen pvUSB frontend (xen hcd) Juergen Gross
[not found] ` <1435042405-14235-3-git-send-email-jgross-IBi9RG/b67k@public.gmane.org>
2015-07-23 9:47 ` David Vrabel
2015-06-23 6:53 ` [Patch V4 3/3] xen: add Xen pvUSB maintainer Juergen Gross
2015-07-20 5:13 ` [Patch V4 0/3] xen, usb: support pvUSB frontend driver Juergen Gross
2016-03-17 19:43 ` Oleksandr Tyshchenko
[not found] ` <CAJEb2DHesrZn0H=d4KVn6sbyXFA8ykdUFMftyAZqbwSKk_JKKQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-18 8:32 ` [Xen-devel] " Juergen Gross
2016-03-18 12:28 ` Oleksandr Tyshchenko
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=20150722234640.GA29425@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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).