From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216697] Resume from suspend stopped working
Date: Thu, 01 Dec 2022 12:57:29 +0000 [thread overview]
Message-ID: <bug-216697-208809-uhPoaPo1CQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216697-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216697
--- Comment #6 from Heikki Krogerus (heikki.krogerus@linux.intel.com) ---
There is a fix for bug 216706, but it hasn't made it into the mainline nor the
stable kernels yet. Can somebody test that fix separately, if it helps with
this bug as well?
https://bugzilla.kernel.org/attachment.cgi?id=303247
--
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-12-01 12:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 8:04 [Bug 216697] New: Resume from suspend stopped working bugzilla-daemon
2022-11-17 9:06 ` [Bug 216697] " bugzilla-daemon
2022-11-17 10:36 ` bugzilla-daemon
2022-11-19 3:02 ` bugzilla-daemon
2022-11-21 10:45 ` bugzilla-daemon
2022-12-01 10:48 ` bugzilla-daemon
2022-12-01 12:57 ` bugzilla-daemon [this message]
2022-12-10 10:59 ` bugzilla-daemon
2022-12-11 10:36 ` bugzilla-daemon
2022-12-21 20:32 ` bugzilla-daemon
2023-01-02 9:41 ` bugzilla-daemon
2023-01-24 16:02 ` bugzilla-daemon
2023-01-25 8:44 ` bugzilla-daemon
2023-01-28 9:23 ` bugzilla-daemon
2023-01-30 9:17 ` bugzilla-daemon
2023-01-30 19:14 ` bugzilla-daemon
2023-02-02 9:07 ` bugzilla-daemon
2023-02-02 9:17 ` bugzilla-daemon
2023-02-02 9:31 ` bugzilla-daemon
2023-02-03 18:39 ` bugzilla-daemon
2023-02-08 7:24 ` bugzilla-daemon
2023-02-08 8:45 ` bugzilla-daemon
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-216697-208809-uhPoaPo1CQ@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