From: merez@codeaurora.org
To: Greg KH <greg@kroah.com>
Cc: Maya Erez <merez@codeaurora.org>,
linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC/PATCH v4] usb: Add streams support to the gadget framework.
Date: Sun, 23 Jan 2011 11:34:19 -0800 (PST) [thread overview]
Message-ID: <e146c388999f324ac94d72d35d4fa656.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <20110120163811.GB30680@kroah.com>
> On Thu, January 20, 2011 8:38 am, Greg KH wrote:
> Why? What in-kernel code needs this?
> Again, why?
Both chnages are required for the UASP device driver
(http://marc.info/?t=129559592400001&r=1&w=2).
Thanks,
Maya Erez
Consultant for Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2011-01-23 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 11:45 [RFC/PATCH v4] usb: Add streams support to the gadget framework Maya Erez
2011-01-20 16:38 ` Greg KH
2011-01-23 19:34 ` merez [this message]
2011-01-23 19:40 ` Greg KH
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=e146c388999f324ac94d72d35d4fa656.squirrel@www.codeaurora.org \
--to=merez@codeaurora.org \
--cc=greg@kroah.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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).