From: patchwork-bot+bluetooth@kernel.org
To: Sebastian Forslund <sebastian.david.forslund@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, sebastif@axis.com
Subject: Re: [PATCH BlueZ v2] Pattern match on service- and manufacturer data
Date: Fri, 08 Dec 2023 15:00:30 +0000 [thread overview]
Message-ID: <170204763019.28520.7832975435305918666.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231207061900.194-1-sebastif@axis.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 7 Dec 2023 07:19:00 +0100 you wrote:
> When advertisement monitoring, manufacturer data and service data was
> not being matched against. This made it so that advertisement monitoring
> with or_patterns did not work that type of data.
>
> We must start matching against the data in the manufacturer_data and
> service_data queues. Run a different match-function depending on the
> type of monitor that is being matched against.
>
> [...]
Here is the summary with links:
- [BlueZ,v2] Pattern match on service- and manufacturer data
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b0656c2cf14d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-12-08 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 6:19 [PATCH BlueZ v2] Pattern match on service- and manufacturer data Sebastian Forslund
2023-12-07 7:31 ` [BlueZ,v2] " bluez.test.bot
2023-12-07 9:09 ` [PATCH BlueZ v2] " Sebastian Forslund
2023-12-07 10:05 ` [BlueZ,v2] " bluez.test.bot
2023-12-08 15:00 ` [PATCH BlueZ v2] " patchwork-bot+bluetooth
2023-12-08 15:00 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-06 21:24 Sebastian Forslund
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=170204763019.28520.7832975435305918666.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sebastian.david.forslund@gmail.com \
--cc=sebastif@axis.com \
/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.