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 v2 1/2] shared/gatt-server: Add bt_gatt_server_set_permissions
Date: Thu, 09 Apr 2026 20:00:09 +0000 [thread overview]
Message-ID: <177576480953.1716836.5463745317091281451.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260408201415.488511-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 Wed, 8 Apr 2026 16:14:14 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This adds bt_gatt_server_set_permissions which can be used to
> enabled/disable permission checking before operations which can be
> useful on testing only environment where encryption/pairing is not
> desirable/needed.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/2] shared/gatt-server: Add bt_gatt_server_set_permissions
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=950853f32861
- [BlueZ,v2,2/2] main.conf: Add GATT.Security option
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=516099a9d405
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:[~2026-04-09 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 20:14 [PATCH BlueZ v2 1/2] shared/gatt-server: Add bt_gatt_server_set_permissions Luiz Augusto von Dentz
2026-04-08 20:14 ` [PATCH BlueZ v2 2/2] main.conf: Add GATT.Security option Luiz Augusto von Dentz
2026-04-08 21:10 ` [BlueZ,v2,1/2] shared/gatt-server: Add bt_gatt_server_set_permissions bluez.test.bot
2026-04-09 20:00 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-08 20:13 [PATCH BlueZ v2 1/2] " Luiz Augusto von Dentz
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=177576480953.1716836.5463745317091281451.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