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 v3 1/2] shared/bass: Fix permissions not requiring encryption
Date: Thu, 02 Oct 2025 16:30:09 +0000 [thread overview]
Message-ID: <175942260924.2981110.5494733385154066766.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251002155855.241787-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, 2 Oct 2025 11:58:54 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> Both Broadcast Audio Scan Control Point and Broadcast Receive State do
> require encryption:
>
> https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/24670-BASS-html5/out/en/index-en.html#UUID-dd95da9a-6ac0-3f45-7e34-13fa9e04d41c
>
> [...]
Here is the summary with links:
- [BlueZ,v3,1/2] shared/bass: Fix permissions not requiring encryption
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=faca31657e1b
- [BlueZ,v3,2/2] client/player: Set QoS.Encryption if QoS.BCode is set
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=3e55476bf6c8
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:[~2025-10-02 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 15:58 [PATCH BlueZ v3 1/2] shared/bass: Fix permissions not requiring encryption Luiz Augusto von Dentz
2025-10-02 15:58 ` [PATCH BlueZ v3 2/2] client/player: Set QoS.Encryption if QoS.BCode is set Luiz Augusto von Dentz
2025-10-02 16:30 ` patchwork-bot+bluetooth [this message]
2025-10-02 17:33 ` [BlueZ,v3,1/2] shared/bass: Fix permissions not requiring encryption bluez.test.bot
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=175942260924.2981110.5494733385154066766.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