All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Tom Catshoek <tomcatshoek@zeelandnet.nl>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] adapter: Fix crash on UUID discovery filter match
Date: Thu, 09 Jul 2026 15:30:13 +0000	[thread overview]
Message-ID: <178361101314.3546291.13415893544947831209.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260709122704.351232-1-tomcatshoek@zeelandnet.nl>

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu,  9 Jul 2026 14:27:04 +0200 you wrote:
> is_filter_match() looks up each discovery-filter UUID in the queue of
> services parsed from a device advertisement. When that services list was
> migrated from a GSList to a struct queue, the queue_find() call kept
> GLib's g_slist_find_custom() argument order, passing the UUID string
> where queue_find() expects a match function and the comparison function
> where it expects the match data.
> 
> [...]

Here is the summary with links:
  - [BlueZ] adapter: Fix crash on UUID discovery filter match
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=82af2beafc39

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-07-09 15:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 12:27 [PATCH BlueZ] adapter: Fix crash on UUID discovery filter match Tom Catshoek
2026-07-09 14:21 ` Bastien Nocera
2026-07-09 15:00   ` Luiz Augusto von Dentz
2026-07-09 16:21     ` Tom Catshoek
2026-07-09 16:23       ` Luiz Augusto von Dentz
2026-07-09 16:31         ` Tom Catshoek
2026-07-09 14:46 ` [BlueZ] " bluez.test.bot
2026-07-09 15:30 ` 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=178361101314.3546291.13415893544947831209.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=tomcatshoek@zeelandnet.nl \
    /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.