From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 212053] system resumes automatically by the XHCI host controller - Intel N6000
Date: Tue, 21 Jun 2022 07:25:57 +0000 [thread overview]
Message-ID: <bug-212053-208809-SVepAhKoVA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-212053-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=212053
Zhang Rui (rui.zhang@intel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Hibernation/Suspend |USB
Assignee|rui.zhang@intel.com |drivers_usb@kernel-bugs.ker
| |nel.org
Product|Power Management |Drivers
Summary|Intel N6000's PCI bridge |system resumes
|[8086:4dbc] makes a system |automatically by the XHCI
|resume from suspend |host controller - Intel
|automatically |N6000
--
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 parent reply other threads:[~2022-06-21 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-212053-208809@https.bugzilla.kernel.org/>
2022-06-21 7:25 ` bugzilla-daemon [this message]
2023-01-31 8:29 ` [Bug 212053] system resumes automatically by the XHCI host controller - Intel N6000 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-212053-208809-SVepAhKoVA@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