From: "Tanya Brokhman" <tlinder@codeaurora.org>
To: 'Alan Stern' <stern@rowland.harvard.edu>
Cc: gregkh@suse.de, linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org
Subject: RE: [RFC/PATCH 0/4] UASP device driver
Date: Sun, 23 Jan 2011 07:53:25 +0200 [thread overview]
Message-ID: <000001cbbac1$dbd56180$93802480$@org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1101211020550.2195-100000@iolanthe.rowland.org>
> I haven't read the code, and I won't have time to read it for quite a
> while.
>
We'll continue working on the development & testing in the meanwhile. Your
inputs are very important for us so we'll appreciate if you take a look when
you find time. Thank you.
> Nevertheless, the title and the first sentence in the patch description
> contain two errors. First, there is no such thing as UASP. What
> you're talking about is UAS -- USB-Attached SCSI. Second, the patch
> set implements a gadget (or function) driver, not a device driver.
>
> Alan Stern
Thank you for the correction. We're used refereeing to this as UASP (UAS
Protocol) but you're absolutely right. I'll fix the patches description in
the next version I upload.
Tanya Brokhman
next prev parent reply other threads:[~2011-01-23 5:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 7:43 [RFC/PATCH 0/4] UASP device driver Tatyana Brokhman
2011-01-21 15:23 ` Alan Stern
2011-01-23 5:53 ` Tanya Brokhman [this message]
2011-02-11 22:47 ` Sarah Sharp
2011-02-13 6:45 ` Tanya Brokhman
2011-02-14 18:31 ` Sarah Sharp
2011-02-21 6:48 ` UAS gadget driver & UAS host driver [was: Re: [RFC/PATCH 0/4] UASP device driver] Tanya Brokhman
2011-02-21 13:03 ` Matthew Wilcox
[not found] ` <20110221130307.GT3663-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2011-02-21 13:45 ` Tanya Brokhman
2011-02-21 14:58 ` Sarah Sharp
2011-02-21 15:35 ` Tanya Brokhman
2011-02-21 16:22 ` Sarah Sharp
2011-02-21 16:34 ` Alan Stern
2011-03-07 7:11 ` Tanya Brokhman
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='000001cbbac1$dbd56180$93802480$@org' \
--to=tlinder@codeaurora.org \
--cc=gregkh@suse.de \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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.