From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@ci.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RESEND PATCH BlueZ v2 0/2] Add support for signed write command
Date: Mon, 04 Mar 2024 21:00:28 +0000 [thread overview]
Message-ID: <170958602879.11728.9496552961788201433.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240304155839.48888-1-frederic.danis@collabora.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 4 Mar 2024 16:58:37 +0100 you wrote:
> GAP/SEC/CSIGN/BV-02-C request the ability to check that signed write has
> been performed successfully.
>
> Move the storage of local and remote CSRK keys to the device object.
> This allow to pass GAP/SEC/CSIGN/BV-01-C and GAP/SEC/CSIGN/BV-02-C tests.
>
> v1 -> v2: Move CSRK keys storage to device object only
>
> [...]
Here is the summary with links:
- [RESEND,BlueZ,v2,1/2] gatt-server: Add support for signed write command
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=71f0a1e88d9a
- [RESEND,BlueZ,v2,2/2] device: Update local and remote CSRK on management event
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=3eba64ba2c85
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:[~2024-03-04 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 15:58 [RESEND PATCH BlueZ v2 0/2] Add support for signed write command Frédéric Danis
2024-03-04 15:58 ` [RESEND PATCH BlueZ v2 1/2] gatt-server: " Frédéric Danis
2024-03-04 17:25 ` bluez.test.bot
2024-03-04 15:58 ` [RESEND PATCH BlueZ v2 2/2] device: Update local and remote CSRK on management event Frédéric Danis
2024-03-04 21: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=170958602879.11728.9496552961788201433.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc==?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@ci.codeaurora.org \
--cc=linux-bluetooth@vger.kernel.org \
/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.