From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 198993] Intel Bluetooth 8260: Spurious wake events prevent from staying suspended in s2idle state on Dell Latitude 7275
Date: Tue, 12 May 2020 21:13:04 +0000 [thread overview]
Message-ID: <bug-198993-62941-Pi75wJlY83@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198993-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198993
Jérôme de Bretagne (jerome.debretagne@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |abhishekpandit@chromium.org
--- Comment #4 from Jérôme de Bretagne (jerome.debretagne@gmail.com) ---
Thanks a lot Abhishek.
The spurious events are going to be fixed with your patch series:
https://lore.kernel.org/patchwork/cover/1208369/
with the 4 commits from 9952d90ea2885d7cbf80cd233f694f09a9c0eaec up to
4867bd007d25a8dfd4ffc558534f7aec8b361789
This series is being planned for v5.7, included from rc1 up to rc5 so far.
I've just tested it using the bluetooth-next tree, and I can confirm that this
is fixing this bug. I'll close and mark it as fixed once v5.7 is released.
Eager to see the 2nd part land to, allowing to set/unset a device as wakeable.
Cheers, Jérôme
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-05-12 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-198993-62941@https.bugzilla.kernel.org/>
2020-05-10 14:19 ` [Bug 198993] Intel Bluetooth 8260: Spurious wake events prevent from staying suspended in s2idle state on Dell Latitude 7275 bugzilla-daemon
2020-05-12 21:13 ` bugzilla-daemon [this message]
2020-07-06 20:29 ` bugzilla-daemon
2020-07-06 20:41 ` bugzilla-daemon
2020-07-06 21:00 ` 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-198993-62941-Pi75wJlY83@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@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 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.