From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 85161] Bluetooth: hci0 SCO packet for unknown connection handle 41
Date: Mon, 26 Oct 2020 21:00:08 +0000 [thread overview]
Message-ID: <bug-85161-62941-v5w5CnGsAZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-85161-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=85161
+1(386) 361-8433 (montegom7@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |montegom7@gmail.com
--- Comment #5 from +1(386) 361-8433 (montegom7@gmail.com) ---
working had is the key
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-10-26 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-85161-62941@https.bugzilla.kernel.org/>
2020-09-30 14:03 ` [Bug 85161] Bluetooth: hci0 SCO packet for unknown connection handle 41 bugzilla-daemon
2020-09-30 14:04 ` bugzilla-daemon
2020-09-30 14:04 ` bugzilla-daemon
2020-10-26 21:00 ` bugzilla-daemon [this message]
2023-09-05 10:06 ` 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-85161-62941-v5w5CnGsAZ@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).