From: merez@codeaurora.org
To: merez@codeaurora.org
Cc: Greg KH <gregkh@suse.de>, Greg KH <greg@kroah.com>,
linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org,
David Brownell <dbrownell@users.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH v2] usb: Add streams support to epautoconf.
Date: Mon, 27 Dec 2010 23:23:19 -0800 (PST) [thread overview]
Message-ID: <aa7e809fb4e353906ded7e89ab7812b0.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <37bcadfd86f17826a034a538b2ade8cd.squirrel@www.codeaurora.org>
>> On Wed, Dec 22, 2010 at 03:58AM, Maya Erez wrote:
> We beleive that the chip-specific code for net2280 and goku at the
> beginning of usb_ep_autoconfig can be moved to this new gadget op,
> therefore it is also needed for today's implementation. I will do the
> cahnge and send a new patch for review
Since the unique implementation of net2280 and goku don't cover all EPs
types and since we don't have the ability to fully test it, we didn't feel
confident to do the changes in their code. Therefore, we decided to remove
the new gadget_op.
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:[~2010-12-28 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 13:46 [RFC/PATCH v2] usb: Add streams support to epautoconf merez
2010-12-21 17:58 ` Greg KH
2010-12-22 11:58 ` merez
2010-12-28 7:23 ` merez [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-20 19:33 merez
2010-12-20 19:58 ` Greg KH
2010-12-16 7:34 Maya Erez
2010-12-16 18:15 ` 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=aa7e809fb4e353906ded7e89ab7812b0.squirrel@www.codeaurora.org \
--to=merez@codeaurora.org \
--cc=dbrownell@users.sourceforge.net \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--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).