From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 217023] [Intel AX200] hci0: Malformed MSFT vendor event: 0x02
Date: Fri, 10 Mar 2023 07:54:03 +0000 [thread overview]
Message-ID: <bug-217023-62941-w3ZcjKy385@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217023-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217023
Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pmenzel+bugzilla.kernel.org
| |@molgen.mpg.de
--- Comment #3 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
@Mathias, please create a separate issue for the regression also attaching the
btmon logs with both Linux kernel versions. Please mention the bug report
number in here.
(Best would be, if you could bisect the regression. Ubuntu offers Linux kernel
mainline builds [1], which make for a good start.)
[1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/
--
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:[~2023-03-10 7:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 11:27 [Bug 217023] New: [Intel AX200] hci0: Malformed MSFT vendor event: 0x02 bugzilla-daemon
2023-03-01 15:53 ` [Bug 217023] " bugzilla-daemon
2023-03-10 7:27 ` bugzilla-daemon
2023-03-10 7:54 ` bugzilla-daemon [this message]
2023-04-20 9:27 ` bugzilla-daemon
2023-04-26 4:41 ` bugzilla-daemon
2023-07-25 11:49 ` bugzilla-daemon
2023-07-25 18:44 ` bugzilla-daemon
2023-08-18 10:00 ` bugzilla-daemon
2023-10-05 0:21 ` bugzilla-daemon
2024-03-29 17:59 ` bugzilla-daemon
2024-09-11 2:37 ` bugzilla-daemon
2024-10-25 6:46 ` bugzilla-daemon
2025-02-11 0:24 ` bugzilla-daemon
2025-02-11 15:10 ` 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-217023-62941-w3ZcjKy385@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;
as well as URLs for NNTP newsgroup(s).