From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Zeng Tao <prime.zeng@hisilicon.com>
Cc: Zeng Tao <prime.zeng@hisilicon.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: dwc3: gadget: don't remove the request if bus-expired
Date: Mon, 14 Jan 2019 10:12:56 +0200 [thread overview]
Message-ID: <87won7mzcn.fsf@linux.intel.com> (raw)
In-Reply-To: <1545339230-10520-1-git-send-email-prime.zeng@hisilicon.com>
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
Hi,
Zeng Tao <prime.zeng@hisilicon.com> writes:
> We have already returned EAGAIN for bus-expiry, and it's designed to
> start with a future Frame number and start the transfer again. So we
> should not remove the request for that case.
>
> Signed-off-by: Zeng Tao <prime.zeng@hisilicon.com>
Do we need a Fixes tag here? How about Cc stable? Can you share
tracepoints exposing the problem?
thanks
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-01-14 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 20:53 [PATCH] usb: dwc3: gadget: don't remove the request if bus-expired Zeng Tao
2019-01-14 8:12 ` Felipe Balbi [this message]
2019-01-21 1:49 ` Zengtao (B)
2019-01-21 9:03 ` 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=87won7mzcn.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=prime.zeng@hisilicon.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).