From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] FL1009: xHCI host not responding to stop endpoint command.
Date: Wed, 22 Jan 2014 17:26:41 -0500 [thread overview]
Message-ID: <20140122222641.GD29184@titan.lakedaemon.net> (raw)
In-Reply-To: <87bnz364h0.fsf@natisbad.org>
On Wed, Jan 22, 2014 at 11:23:23PM +0100, Arnaud Ebalard wrote:
> With the patch applied on top of 3.13.0 kernel recompiled w/
> CONFIG_PCI_MSI enabled, I cannot reproduce the bug. I guess
> you can add my:
>
> Reported-and-tested-By: Arnaud Ebalard <arno@natisbad.org>
>
> Since you'll have to push the patch to -stable team at least for 3.13,
> I wonder if it would not make sense to extend that at least to 3.12.
> and possibly 3.10 (3.2 is still widely used but I wonder if it makes
> sense to go that far).
Can you pinpoint the commit that introduced the regression?
thx,
Jason.
next prev parent reply other threads:[~2014-01-22 22:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 20:13 [BUG] FL1009: xHCI host not responding to stop endpoint command Arnaud Ebalard
2014-01-12 21:36 ` Arnaud Ebalard
2014-01-14 17:07 ` Sarah Sharp
2014-01-14 18:11 ` Bjørn Mork
2014-01-14 21:54 ` Arnaud Ebalard
2014-01-15 9:59 ` David Laight
2014-01-15 19:04 ` Arnaud Ebalard
2014-01-16 18:50 ` Sarah Sharp
2014-01-17 6:25 ` Arnaud Ebalard
2014-01-17 8:31 ` Bjørn Mork
2014-01-17 20:54 ` Sarah Sharp
2014-01-18 21:49 ` Arnaud Ebalard
2014-01-21 21:17 ` Sarah Sharp
2014-01-22 22:23 ` Arnaud Ebalard
2014-01-22 22:26 ` Jason Cooper [this message]
2014-01-22 22:43 ` Arnaud Ebalard
2014-01-22 23:56 ` Sarah Sharp
2014-01-23 8:24 ` Arnaud Ebalard
2014-01-23 11:09 ` Willy Tarreau
2014-01-27 22:20 ` Arnaud Ebalard
2014-01-26 13:30 ` Thomas Petazzoni
2014-01-27 18:36 ` Arnaud Ebalard
2014-02-10 18:57 ` Arnaud Ebalard
2014-02-14 0:09 ` Sarah Sharp
2014-02-14 8:26 ` Thomas Petazzoni
2014-02-18 13:10 ` Thomas Petazzoni
2014-02-18 20:54 ` Arnaud Ebalard
2014-02-18 21:24 ` Thomas Petazzoni
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=20140122222641.GD29184@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.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).