From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216706] USBC resume callback takes far too long, between 650ms and 1200ms
Date: Fri, 18 Nov 2022 20:24:54 +0000 [thread overview]
Message-ID: <bug-216706-208809-tZaGytkQCs@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216706-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216706
--- Comment #1 from Todd Brandt (todd.e.brandt@intel.com) ---
Created attachment 303219
--> https://bugzilla.kernel.org/attachment.cgi?id=303219&action=edit
lenb-Dell-XPS-13-9315_freeze.html
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-11-18 20:25 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 ` bugzilla-daemon [this message]
2022-11-18 20:25 ` [Bug 216706] " 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 ` [Bug 216706] New: " Greg KH
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=bug-216706-208809-tZaGytkQCs@https.bugzilla.kernel.org/ \
--to=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).