From: Alan Stern <stern@rowland.harvard.edu>
To: Rajesh Bhagat <rajesh.bhagat@nxp.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"mathias.nyman@intel.com" <mathias.nyman@intel.com>,
Sriram Dash <sriram.dash@nxp.com>
Subject: RE: [PATCH] usb: xhci: Fix incomplete PM resume operation due to XHCI commmand timeout
Date: Mon, 21 Mar 2016 11:02:58 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1603211102080.1708-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <HE1PR0401MB2028724EAC68D97679A79B74E38F0@HE1PR0401MB2028.eurprd04.prod.outlook.com>
On Mon, 21 Mar 2016, Rajesh Bhagat wrote:
> I agree to your point. Actually the intent was to check the return status of reset_device which
> is currently being ignored. I encountered the reset_device failure case in resume operation (STR)
> which is increasing the time of resume and causing unexpected crashes if return value is not checked.
>
> Do you agree it should be checked here? If yes, I can rework this patch.
I don't know. You should ask the xHCI maintainter, Mathias.
Alan Stern
prev parent reply other threads:[~2016-03-21 15:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 7:01 [PATCH] usb: xhci: Fix incomplete PM resume operation due to XHCI commmand timeout Rajesh Bhagat
2016-03-18 11:20 ` Mathias Nyman
2016-03-21 4:18 ` Rajesh Bhagat
2016-03-21 9:16 ` Mathias Nyman
2016-03-22 5:19 ` Rajesh Bhagat
2016-03-22 12:05 ` Mathias Nyman
2016-03-23 3:53 ` Rajesh Bhagat
2016-03-23 14:22 ` Mathias Nyman
2016-03-28 6:13 ` Rajesh Bhagat
2016-03-29 17:21 ` Mathias Nyman
2016-03-31 3:51 ` Rajesh Bhagat
2016-03-31 14:36 ` Mathias Nyman
2016-04-01 3:55 ` Rajesh Bhagat
2016-04-01 10:49 ` Mathias Nyman
2016-04-11 3:46 ` Rajesh Bhagat
2016-03-18 14:21 ` Alan Stern
2016-03-21 4:22 ` Rajesh Bhagat
2016-03-21 15:02 ` Alan Stern [this message]
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.1603211102080.1708-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=rajesh.bhagat@nxp.com \
--cc=sriram.dash@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.