From: Jeremy White <jwhite@codeweavers.com>
To: "Sean O. Stalley" <sean.stalley@intel.com>
Cc: Greg KH <greg@kroah.com>,
stephanie.s.wallick@intel.com,
Alex Elsayed <eternaleye@gmail.com>,
linux-usb@vger.kernel.org, spice-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] Add a usbredir kernel module to remotely connect USB devices over IP.
Date: Wed, 22 Jul 2015 19:20:31 -0500 [thread overview]
Message-ID: <55B0334F.3000609@codeweavers.com> (raw)
In-Reply-To: <20150722175950.GA3928@sean.stalley.intel.com>
On 07/22/2015 12:59 PM, Sean O. Stalley wrote:
> On Wed, Jul 22, 2015 at 11:55:32AM -0500, Jeremy White wrote:
>> I privately wrote to the Intel authors of that patch a week ago; I've
>> publicly included them in this thread as well. As far as I can tell,
>> they've been silent on this front since November; I fear that they may
>> have moved on, or that Intel is not actively working on this. None of
>> the Intel authors listed on the MA-USB specification are kernel
>> contributors, so I did not have a way to reach out to them. If you have
>> the means to engage others, I would appreciate that.
>
> Sorry for the delay. The short answer is: Yes, we have been actively working on this driver.
> Per Greg KH's request, we have been cleaning up the driver internally.
> There was a lot to clean up, which is why we have been silent on LKML.
Great, thanks. I would appreciate a chance to work with you to make
sure it will work well for XSpice. I'm happy to help as much as I can,
and please don't feel the need to wait for a final version before
reaching out to me.
Cheers,
Jeremy
next prev parent reply other threads:[~2015-07-23 0:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 21:44 [RFC PATCH 0/1] RFC - Implement a usbredir kernel module Jeremy White
2015-06-30 21:44 ` [RFC PATCH 1/1] Add a usbredir kernel module to remotely connect USB devices over IP Jeremy White
2015-06-30 23:48 ` Greg KH
2015-07-01 3:34 ` Jeremy White
2015-07-01 5:44 ` Greg KH
2015-07-01 15:55 ` Jeremy White
2015-07-01 16:13 ` Greg KH
2015-07-01 18:39 ` Hans de Goede
2015-07-07 16:47 ` Jeremy White
2015-07-08 7:11 ` Hans de Goede
2015-07-09 0:19 ` Jeremy White
2015-07-01 9:06 ` [Spice-devel] " Daniel P. Berrange
2015-07-01 18:31 ` Jeremy White
2015-07-01 18:45 ` Hans de Goede
2015-07-02 8:45 ` Oliver Neukum
2015-07-02 11:35 ` Hans de Goede
2015-07-02 12:10 ` Oliver Neukum
2015-07-02 15:57 ` Jeremy White
2015-07-02 18:46 ` Oliver Neukum
2015-07-02 19:02 ` Jeremy White
2015-07-02 19:59 ` Alan Stern
2015-07-02 20:06 ` Jeremy White
2015-07-02 20:20 ` Alan Stern
2015-07-03 8:51 ` Krzysztof Opasiak
2015-07-03 14:04 ` Alan Stern
2015-07-06 8:20 ` Oliver Neukum
2015-07-06 20:14 ` Jeremy White
2015-07-06 20:22 ` Alan Stern
[not found] ` <mnlh2b$1cs$1@ger.gmane.org>
2015-07-22 14:03 ` Jeremy White
2015-07-22 14:34 ` Greg KH
2015-07-22 16:55 ` Jeremy White
2015-07-22 17:59 ` Sean O. Stalley
2015-07-23 0:20 ` Jeremy White [this message]
2015-12-09 22:32 ` Jeremy White
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=55B0334F.3000609@codeweavers.com \
--to=jwhite@codeweavers.com \
--cc=eternaleye@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sean.stalley@intel.com \
--cc=spice-devel@lists.freedesktop.org \
--cc=stephanie.s.wallick@intel.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