Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-474-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH BlueZ v2] Pattern match on service- and manufacturer data
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <170204763019.28520.7832975435305918666.git-patchwork-notify@kernel.org>
Date: Fri, 08 Dec 2023 15:00:30 +0000
References: <20231207061900.194-1-sebastif@axis.com>
In-Reply-To: <20231207061900.194-1-sebastif@axis.com>
To: Sebastian Forslund <sebastian.david.forslund@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, 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