From: patchwork-bot+bluetooth@kernel.org
To: Hex Lindqvist <hex@freenixos.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, pmenzel@molgen.mpg.de,
abhishekpandit@chromium.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btintel: Don't log unsupported debug features as an error
Date: Tue, 17 Nov 2026 18:50:12 +0000 [thread overview]
Message-ID: <179494141227.761488.17080097216959438759.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261113222024.1123279-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 Fri, 13 Nov 2026 14:20:24 -0800 you wrote:
> Since commit af395330abed ("Bluetooth: btintel: Add Intel devcoredump
> support"), setup sends Read Supported Features (0xfca6) to decide
> whether to register devcoredump. Older controllers such as the 8260
> and 8265 reject it with Command Disallowed, so every probe logs:
>
> Bluetooth: hci0: Reading supported features failed (-16)
> Bluetooth: hci0: Error reading debug features
>
> [...]
Here is the summary with links:
- Bluetooth: btintel: Don't log unsupported debug features as an error
https://git.kernel.org/bluetooth/bluetooth-next/c/b05fb50e255a
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-17 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 22:20 [PATCH] Bluetooth: btintel: Don't log unsupported debug features as an error Hex Lindqvist
2026-11-14 3:03 ` bluez.test.bot
2026-11-17 18:50 ` 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=179494141227.761488.17080097216959438759.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=abhishekpandit@chromium.org \
--cc=hex@freenixos.com \
--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.