From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 199271] AR3012 [0cf3:3004] - Bluetooth: hci0: don't support firmware rome 0x31010000.
Date: Mon, 14 Dec 2020 10:12:51 +0000 [thread overview]
Message-ID: <bug-199271-62941-qCPk1FASe0@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199271-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199271
--- Comment #17 from Hans de Goede (jwrdegoede@fedoraproject.org) ---
(In reply to anthony from comment #16)
> After upgrade kernel to version 5.10:
>
> kernel: Bluetooth: hci0: don't support firmware rome 0x31010000
>
> previous kernel 5.9.13 was ok.
The last activity on this bug was more then 2 years ago, so this sounds like a
comletely new (introduced in 5.10) and unrelated problem. Please file a new bug
for this.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2020-12-14 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199271-62941@https.bugzilla.kernel.org/>
2020-12-14 8:48 ` [Bug 199271] AR3012 [0cf3:3004] - Bluetooth: hci0: don't support firmware rome 0x31010000 bugzilla-daemon
2020-12-14 10:12 ` bugzilla-daemon [this message]
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-199271-62941-qCPk1FASe0@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).