From: George Cherian <george.cherian@ti.com>
To: Tony Lindgren <tony@atomide.com>, Daniel Mack <daniel@zonque.org>
Cc: linux-usb@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: Gadget regression with enabling of MUSB babble interrupt handling
Date: Fri, 20 Jun 2014 09:11:53 +0530 [thread overview]
Message-ID: <53A3AD81.10109@ti.com> (raw)
In-Reply-To: <20140619112455.GE29055@atomide.com>
On 6/19/2014 4:54 PM, Tony Lindgren wrote:
> * Daniel Mack <daniel@zonque.org> [140619 03:51]:
>> On 06/19/2014 12:43 PM, Tony Lindgren wrote:
>>> * Daniel Mack <daniel@zonque.org> [140619 03:38]:
>>>> On 06/19/2014 12:31 PM, Tony Lindgren wrote:
>>>>> * Daniel Mack <daniel@zonque.org> [140619 03:10]:
>>>>>> On 06/19/2014 11:56 AM, Tony Lindgren wrote:
>>>>> But that also raises a question: Were these patches merged for
>>>>> v3.16 ever even tested in peripheral mode?
>>>> At the time, I had no such hardware to test this on, so I was hoping for
>>>> more testers to give them a try in different environments, which
>>>> apparently didn't happen. It fixed a dead USB port condition on
>>>> host-mode enabled hardware, though.
>>> Well we probably should not merge patches without proper acks and
>>> tested-by:s in general as things just seem to keep breaking
>>> constantly otherwise. And things not working will keep people from
>>> using linux next which will lead into even less testing..
>> I'm fairly sure the patch causing your trouble has been in linux-next
>> for a while before they hit the merge window, so people with gadget
>> enabled musb could have noticed the breakage early enough. The feedback
>> rate for patches to this driver posted to linux-usb is also usually low,
>> unfortunately.
I blame myself for not explicitly pointing out the fix.
Instead I clubbed it with this series.
http://marc.info/?l=linux-usb&m=140109627505065&w=4
Sorry for that.
> Right but the problem is that people are not touching linux next
> because it's constantly broken :)
>
>> Anyway, breaking things is certainly not good, and I'm sorry for that.
>> I'm just uncertain what detail in the procedure should be tweaked in
>> order to prevent that from happening in the future.
> Well I guess somebody should run basic tests on this driver in
> linux next, that would probably solve the issues.
I am doing it.
> Regards,
>
> Tony
--
-George
next prev parent reply other threads:[~2014-06-20 3:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 9:56 Gadget regression with enabling of MUSB babble interrupt handling Tony Lindgren
[not found] ` <20140619095655.GA29055-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-06-19 10:08 ` Daniel Mack
2014-06-19 10:31 ` Tony Lindgren
2014-06-19 10:36 ` Daniel Mack
[not found] ` <53A2BD34.1060409-cYrQPVfZoowdnm+yROfE0A@public.gmane.org>
2014-06-19 10:43 ` Tony Lindgren
[not found] ` <20140619104324.GC29055-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-06-19 10:50 ` Daniel Mack
2014-06-19 11:24 ` Tony Lindgren
2014-06-20 3:41 ` George Cherian [this message]
2014-06-20 6:20 ` Tony Lindgren
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=53A3AD81.10109@ti.com \
--to=george.cherian@ti.com \
--cc=balbi@ti.com \
--cc=daniel@zonque.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=tony@atomide.com \
/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).