From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 186201] Bluetooth kernel oops on suspend following resume - Lenoveo Yoga900, Dell Latitude E7270
Date: Mon, 21 Nov 2016 14:50:06 +0000 [thread overview]
Message-ID: <bug-186201-62941-zu0rRktgZz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-186201-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=186201
Len Brown <lenb@kernel.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|kernel oops upon second |Bluetooth kernel oops on
|suspend to mem - Lenoveo |suspend following resume -
|Yoga900 |Lenoveo Yoga900, Dell
| |Latitude E7270
--
You are receiving this mail because:
You are the assignee for the bug.
next parent reply other threads:[~2016-11-21 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-186201-62941@https.bugzilla.kernel.org/>
2016-11-21 14:50 ` bugzilla-daemon [this message]
2016-11-21 14:55 ` [Bug 186201] Bluetooth kernel oops on suspend following resume - Lenoveo Yoga900, Dell Latitude E7270 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-186201-62941-zu0rRktgZz@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 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).