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 1/3] gatt: Fix not setting permissions for CCC
Date: Thu, 22 Sep 2022 01:10:21 +0000 [thread overview]
Message-ID: <166380902197.22214.662103270812215678.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220921214656.2241730-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, 21 Sep 2022 14:46:54 -0700 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> CCC shall always have both Read and Write permissions set in addition to
> what application set.
>
> Fixes: https://github.com/bluez/bluez/issues/399
>
> [...]
Here is the summary with links:
- [BlueZ,1/3] gatt: Fix not setting permissions for CCC
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=fbf17ac497bb
- [BlueZ,2/3] gatt-db: Check if permissions are set when adding CCC
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=50782b0eeb05
- [BlueZ,3/3] client/gatt: Fix notification enabled/disabled output
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c2734c41f7c0
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:[~2022-09-22 1:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 21:46 [PATCH BlueZ 1/3] gatt: Fix not setting permissions for CCC Luiz Augusto von Dentz
2022-09-21 21:46 ` [PATCH BlueZ 2/3] gatt-db: Check if permissions are set when adding CCC Luiz Augusto von Dentz
2022-09-21 21:46 ` [PATCH BlueZ 3/3] client/gatt: Fix notification enabled/disabled output Luiz Augusto von Dentz
2022-09-21 23:09 ` [BlueZ,1/3] gatt: Fix not setting permissions for CCC bluez.test.bot
2022-09-22 1:10 ` 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=166380902197.22214.662103270812215678.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