From: patchwork-bot+bluetooth@kernel.org
To: Thomas de Gruijter <thomasdegruijter@pm.me>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, brian.gix@intel.com,
howardchung@google.com, mcchou@chromium.org,
apusaka@chromium.org, luiz.von.dentz@intel.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Bluetooth: MSFT: Only enable the advertisement filter with monitors
Date: Fri, 20 Nov 2026 17:20:05 +0000 [thread overview]
Message-ID: <179519520528.673037.13658094971187951302.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261120-msft-filter-monitors-v1-0-8192f0c0791a@pm.me>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 20 Nov 2026 02:13:34 +0100 you wrote:
> On MediaTek MT7922 (USB 0e8d:0616, BT firmware build 20260724) LE
> discovery and passive scanning find nothing, because msft_do_open()
> enables the MSFT advertisement filter on every power on even when no
> advertisement monitor is registered, and this controller then drops
> every advertisement.
>
> Patch 2 only enables the filter while at least one monitor is offloaded.
> It is the first user of msft->filter_enabled, which does not follow the
> controller when it reports the filter as already being in the requested
> state, so patch 1 fixes that first.
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: MSFT: Record the filter state on Command Disallowed
https://git.kernel.org/bluetooth/bluetooth-next/c/75d6b9d82c35
- [2/2] Bluetooth: MSFT: Only enable the advertisement filter with monitors
https://git.kernel.org/bluetooth/bluetooth-next/c/4a8f9b7fb4f5
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-20 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 1:13 [PATCH 0/2] Bluetooth: MSFT: Only enable the advertisement filter with monitors Thomas de Gruijter
2026-11-20 1:13 ` Thomas de Gruijter via B4 Relay
2026-11-20 1:13 ` [PATCH 1/2] Bluetooth: MSFT: Record the filter state on Command Disallowed Thomas de Gruijter via B4 Relay
2026-11-20 1:13 ` Thomas de Gruijter
2026-11-20 4:51 ` Bluetooth: MSFT: Only enable the advertisement filter with monitors bluez.test.bot
2026-11-20 1:13 ` [PATCH 2/2] " Thomas de Gruijter
2026-11-20 1:13 ` Thomas de Gruijter via B4 Relay
2026-11-20 17:20 ` 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=179519520528.673037.13658094971187951302.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=apusaka@chromium.org \
--cc=brian.gix@intel.com \
--cc=howardchung@google.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=mcchou@chromium.org \
--cc=thomasdegruijter@pm.me \
/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.