From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1 1/3] adapter: Fix exposing coordinate sets if LE Audio is disabled
Date: Fri, 06 Jun 2025 19:00:28 +0000 [thread overview]
Message-ID: <174923642875.3945689.16726314393463860699.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250605181256.853484-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 5 Jun 2025 14:12:54 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This fixes exposing non-discoverable coordinate set members if LE Audio
> is disabled since it may lead system device setting showing them to user
> that may attempt to pair them and end up not working.
>
> Fixes: https://github.com/bluez/bluez/issues/523
>
> [...]
Here is the summary with links:
- [BlueZ,v1,1/3] adapter: Fix exposing coordinate sets if LE Audio is disabled
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4a7ee30978da
- [BlueZ,v1,2/3] client: Add assistant.list
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=04c32f3d3129
- [BlueZ,v1,3/3] client: Add assistant.show
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f09f33199858
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:[~2025-06-06 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 18:12 [PATCH BlueZ v1 1/3] adapter: Fix exposing coordinate sets if LE Audio is disabled Luiz Augusto von Dentz
2025-06-05 18:12 ` [PATCH BlueZ v1 2/3] client: Add assistant.list Luiz Augusto von Dentz
2025-06-05 18:12 ` [PATCH BlueZ v1 3/3] client: Add assistant.show Luiz Augusto von Dentz
2025-06-05 20:09 ` [BlueZ,v1,1/3] adapter: Fix exposing coordinate sets if LE Audio is disabled bluez.test.bot
2025-06-06 19:00 ` 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=174923642875.3945689.16726314393463860699.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox