From: Greg KH <gregkh@linuxfoundation.org>
To: bugzilla-daemon@kernel.org
Cc: linux-usb@vger.kernel.org
Subject: Re: [Bug 216706] New: USBC resume callback takes far too long, between 650ms and 1200ms
Date: Sat, 19 Nov 2022 09:53:48 +0100 [thread overview]
Message-ID: <Y3iZnMq5mGyEmZv9@kroah.com> (raw)
In-Reply-To: <bug-216706-208809@https.bugzilla.kernel.org/>
On Fri, Nov 18, 2022 at 08:24:14PM +0000, bugzilla-daemon@kernel.org wrote:
> I have timelines from 7 separate machines that are now affected but this
> behavior. We have a guidline that neither suspend or resume should take longer
> than a second, and this is causing us problems.
What is making this arbritrary requirement? If it is an issue, please
provide a working change to resolve it as your group can help implement
and test this.
thanks,
greg k-h
prev parent reply other threads:[~2022-11-19 8:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 20:24 [Bug 216706] New: USBC resume callback takes far too long, between 650ms and 1200ms bugzilla-daemon
2022-11-18 20:24 ` [Bug 216706] " bugzilla-daemon
2022-11-18 20:25 ` bugzilla-daemon
2022-11-18 20:25 ` bugzilla-daemon
2022-11-18 20:26 ` bugzilla-daemon
2022-11-18 20:26 ` bugzilla-daemon
2022-11-18 20:26 ` bugzilla-daemon
2022-11-19 8:53 ` Greg KH [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=Y3iZnMq5mGyEmZv9@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bugzilla-daemon@kernel.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).