From: Alan Stern <stern@rowland.harvard.edu>
To: Erkka Talvitie <erkka.talvitie@vincit.fi>
Cc: gregkh@linuxfoundation.org, <linux-usb@vger.kernel.org>,
<claus.baumgartner@med.ge.com>
Subject: RE: [RFCv1 1/1] USB: EHCI: Do not return -EPIPE when hub is disconnected
Date: Mon, 9 Dec 2019 10:24:45 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1912091024060.1462-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <023701d5ae77$14ec9d50$3ec5d7f0$@vincit.fi>
On Mon, 9 Dec 2019, Erkka Talvitie wrote:
> > Ok, just to double check:
> >
> > I take the existing driver code (I will not apply the earlier RFC on top
> of
> > that) and apply one more check before the original stall check (that is):
> > } else if (QTD_CERR(token)) {
> >
> > The check that I will add is checking MMF bit && PID == IN, and this check
> > comes right after the babble check, right?
> >
> > Good, seems like a simple change. Yet I still prefer to test the change.
> > Unfortunately that goes to the next week as we have a national holiday
> > tomorrow.
> > I will get back to you most likely on Monday.
>
> I tested this change and it removes the error messages from the output.
Great! Okay, feel free to submit a new patch.
Alan Stern
next prev parent reply other threads:[~2019-12-09 15:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 14:08 [RFCv1 1/1] USB: EHCI: Do not return -EPIPE when hub is disconnected Erkka Talvitie
2019-12-02 19:43 ` Alan Stern
2019-12-03 9:38 ` Erkka Talvitie
2019-12-03 10:54 ` Erkka Talvitie
2019-12-03 13:35 ` Erkka Talvitie
2019-12-03 19:01 ` Alan Stern
2019-12-04 8:55 ` Erkka Talvitie
2019-12-04 13:18 ` Erkka Talvitie
2019-12-04 14:24 ` Alan Stern
2019-12-04 14:37 ` Erkka Talvitie
2019-12-05 10:35 ` Erkka Talvitie
2019-12-05 14:37 ` Alan Stern
2019-12-05 15:00 ` Erkka Talvitie
2019-12-09 9:57 ` Erkka Talvitie
2019-12-09 15:24 ` Alan Stern [this message]
2019-12-10 6:31 ` Erkka Talvitie
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=Pine.LNX.4.44L0.1912091024060.1462-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=claus.baumgartner@med.ge.com \
--cc=erkka.talvitie@vincit.fi \
--cc=gregkh@linuxfoundation.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).