From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>,
Michal Nazarewicz <mina86@mina86.com>
Cc: Tony Lindgren <tony@atomide.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Bin Liu <b-liu@ti.com>,
pali.rohar@gmail.com
Subject: Re: [PATCH] usb: f_mass_storage: test whether thread is running before starting another
Date: Thu, 7 Apr 2016 17:46:40 +0300 [thread overview]
Message-ID: <570672D0.4010102@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1604071024100.2179-100000@iolanthe.rowland.org>
Hi,
On 7.04.2016 17:25, Alan Stern wrote:
> On Thu, 7 Apr 2016, Michal Nazarewicz wrote:
>
>> Sounds good to me. I’d love someone to test this patch (I sadly have no
>> way of doing that at the moment) and with that I can resend it with
>> updated message.
>
> Ivaylo should be able to try it.
>
I applied the patch agains 4.6-rc1 and while it seems there is no more
oops, trying to "cd /sys/bus/platform/drivers/musb-hdrc && echo
musb-hdrc.0.auto > unbind" still results in console hang. Will try to
find time later today and put printks all over the place to see what's
going on.
Ivo
next prev parent reply other threads:[~2016-04-07 14:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 17:28 [PATCH] usb: f_mass_storage: test whether thread is running before starting another Michal Nazarewicz
2016-04-05 17:42 ` Alan Stern
2016-04-05 18:07 ` Michal Nazarewicz
2016-04-05 18:35 ` Alan Stern
2016-04-05 22:26 ` Michal Nazarewicz
2016-04-06 15:05 ` Alan Stern
2016-04-07 9:57 ` Michal Nazarewicz
2016-04-07 14:25 ` Alan Stern
2016-04-07 14:46 ` Ivaylo Dimitrov [this message]
2016-04-07 20:50 ` Ivaylo Dimitrov
2016-04-07 16:40 ` Michal Nazarewicz
2016-04-18 9:26 ` Andrzej Pietrasiewicz
2016-04-19 14:38 ` Michal Nazarewicz
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=570672D0.4010102@gmail.com \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=b-liu@ti.com \
--cc=felipe.balbi@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mina86@mina86.com \
--cc=pali.rohar@gmail.com \
--cc=stern@rowland.harvard.edu \
--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