From: patchwork-bot+bluetooth@kernel.org
To: Hex Lindqvist <hex@freenixos.com>
Cc: brgl@kernel.org, marcel@holtmann.org, luiz.dentz@gmail.com,
pmenzel@molgen.mpg.de, linux-bluetooth@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: qca: Disable SoC debug logging for WCN3990
Date: Mon, 09 Nov 2026 16:00:07 +0000 [thread overview]
Message-ID: <179424000705.3335769.610567076772554344.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261108000449.2664455-1-hex@freenixos.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 7 Nov 2026 16:04:49 -0800 you wrote:
> Unless the host turns it off, the WCN3990 firmware sends debug logs to
> the host as ACL packets on handle 0x2EDC. hci_qca passes them on as
> diagnostic packets, which the core copies to the monitor socket and then
> frees, so nothing appears in the kernel log. btmon shows them as:
>
> = Vendor Diagnostic (len 492) [hci0] 0.761331
> dc 2e e8 01 e4 01 03 00 0a ff 10 04 01 00 55 53
> = Vendor Diagnostic (len 481) [hci0] 11.334015
> dc 2e dd 01 d9 01 04 00 0a ff 10 04 01 00 51 d3
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: qca: Disable SoC debug logging for WCN3990
https://git.kernel.org/bluetooth/bluetooth-next/c/530e411a49f3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-09 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 0:04 [PATCH v2] Bluetooth: qca: Disable SoC debug logging for WCN3990 Hex Lindqvist
2026-11-08 2:24 ` [v2] " bluez.test.bot
2026-11-09 16:00 ` patchwork-bot+bluetooth [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=179424000705.3335769.610567076772554344.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=brgl@kernel.org \
--cc=hex@freenixos.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.