From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215189] hci0: unexpected event for opcode 0xfc2f
Date: Sun, 08 May 2022 19:15:02 +0000 [thread overview]
Message-ID: <bug-215189-62941-naMJGkqQu1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215189-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215189
shwoseph@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |shwoseph@gmail.com
--- Comment #2 from shwoseph@gmail.com ---
I am suffering from this issue as well. It wouldn’t be so bad except that the
message gets printed out to tty1 and messes up my login console on wake from
sleep.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-05-08 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 16:52 [Bug 215189] New: hci0: unexpected event for opcode 0xfc2f bugzilla-daemon
2022-05-08 19:15 ` bugzilla-daemon [this message]
2022-11-27 18:18 ` [Bug 215189] " 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-215189-62941-naMJGkqQu1@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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