From: "Shimrit Malichi" <smalichi@codeaurora.org>
To: balbi@ti.com
Cc: Greg KH <greg@kroah.com>,
Shimrit Malichi <smalichi@codeaurora.org>,
linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org,
ablay@codeaurora.org
Subject: Re: [RFC/PATCH v4 0/3] UAS Gadget Driver.
Date: Wed, 7 Dec 2011 09:34:33 -0800 (PST) [thread overview]
Message-ID: <dbceef1c27984ec023a409618d25504c.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <20111207083912.GG32368@legolas.emea.dhcp.ti.com>
> On Tue, Dec 06, 2011 at 09:09:55AM -0800, Greg KH wrote:
>> On Tue, Dec 06, 2011 at 08:39:58AM -0800, Shimrit Malichi wrote:
>> >
>> > > On Sun, Dec 04, 2011 at 10:18:14PM +0200, Shimrit Malichi wrote:
>> > >> This patch series implements the UAS gadget driver.
>> > >>
>> > >> It has been tested using the following:
>> > >> 1. Linux UAS host driver
>> > >> 2. Internaly developed unittests framework
>> > >>
>> > >> The device is functional. More stress tests are needed.
>> > >>
>> > >> TODO: Further testing
>> > >> De-register the gadget if the main thread dies.
>> > >
>> > > What about all of the review comments you seem to be ignoring that
>> have
>> > > been made for this driver in the past?
>> > >
>> > > greg k-h
>> > >
>> > We addressed most of the comments. One of them was indeed to use the
>> > target framework, however when we asked an additional information
>> about
>> > how to use this framework we didn't get a detailed reply. Sebastian
>> gave
>> > an answer on how to use it yesterday. We will study his answer, and
>> come
>> > up with a new code.
>>
>> No one is going to normally give you such a detailed answer as he did.
>> You were told to go use that interface, and Sebastian did just that, why
>> couldn't you have done that in the first place, saving you, and everyone
>> else here, time and effort of telling you to go do that again?
>
> other than that, it's just waste of time if you go write new code, now
> that Sebastian already has that almost ready. Save yourself sometime and
> just help Sebastian finishing what he's already done. Even testing is
> welcome at this stage.
>
> --
> balbi
>
Hi guys,
Thanks for all your inputs. The good thing is that we now have a better
understanding of the UASP implementation that was done offline, and as
balbi mentioned, probably avoid duplicate work.
We will coordinate with Sebastian regarding the next phases.
Shimrit
--
Consultant for Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2011-12-07 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 20:18 [RFC/PATCH v4 0/3] UAS Gadget Driver Shimrit Malichi
[not found] ` <1323029894-16106-1-git-send-email-smalichi-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2011-12-05 15:55 ` Greg KH
2011-12-06 16:39 ` Shimrit Malichi
2011-12-06 17:09 ` Greg KH
2011-12-07 8:39 ` Felipe Balbi
2011-12-07 17:34 ` Shimrit Malichi [this message]
[not found] ` <dbceef1c27984ec023a409618d25504c.squirrel-mMfbam+mt9083fI46fginR2eb7JE58TQ@public.gmane.org>
2011-12-08 17:37 ` Sebastian Andrzej Siewior
2011-12-21 14:05 ` Shimrit Malichi
2011-12-21 14:27 ` Felipe Balbi
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=dbceef1c27984ec023a409618d25504c.squirrel@www.codeaurora.org \
--to=smalichi@codeaurora.org \
--cc=ablay@codeaurora.org \
--cc=balbi@ti.com \
--cc=greg@kroah.com \
--cc=linux-arm-msm@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).