From: Michal Nazarewicz <mina86@mina86.com>
To: balbi@ti.com, jackp@codeaurora.org, pheatwol@codeaurora.org
Cc: linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org,
benoit@android.com, andrzej.p@samsung.com,
gregkh@linuxfoundation.org, Manu Gautam <mgautam@codeaurora.org>
Subject: Re: [PATCH v6 0/2] usb: gadget: f_fs: Add support for SuperSpeed Mode
Date: Fri, 28 Feb 2014 13:51:01 +0100 [thread overview]
Message-ID: <xa1ta9dbs8ne.fsf@mina86.com> (raw)
In-Reply-To: <1393586423-25387-1-git-send-email-mgautam@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
On Fri, Feb 28 2014, Manu Gautam <mgautam@codeaurora.org> wrote:
> Changes since v5:
> * There is no change in 1st patch.
> * 2nd patch from Michal updates ABI and adds new field - flags which lists
> the descriptors that are present. Driver selects between the schemes based
> on the magic number passed by client.
> With the new scheme, usb_functionfs_descs header is removed and clients
> can selectively pass descriptors and their count based on the 'flags' field.
Thanks for testing and fixes! Looks good to me.
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +--<mpn@google.com>--<xmpp:mina86@jabber.org>--ooO--(_)--Ooo--
[-- Attachment #2.1: Type: text/plain, Size: 0 bytes --]
[-- Attachment #2.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
prev parent reply other threads:[~2014-02-28 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 11:20 [PATCH v6 0/2] usb: gadget: f_fs: Add support for SuperSpeed Mode Manu Gautam
2014-02-28 11:20 ` [PATCH v6 1/2] " Manu Gautam
2014-02-28 11:20 ` [PATCH v6 2/2] usb: gadget: f_fs: Add flags to descriptors block Manu Gautam
2014-02-28 12:51 ` Michal Nazarewicz [this message]
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=xa1ta9dbs8ne.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=andrzej.p@samsung.com \
--cc=balbi@ti.com \
--cc=benoit@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=jackp@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgautam@codeaurora.org \
--cc=pheatwol@codeaurora.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 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).