From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 0/4] device: Fix resolving a coordinated set over Secure Connections
Date: Fri, 18 Sep 2026 16:30:48 +0000 [thread overview]
Message-ID: <178974904814.1035983.12606949586547695456.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1789689632.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 18 Sep 2026 03:02:25 +0300 you wrote:
> CSIP coordinator was not finding its LTKs with Secure Connections, as
> the fix in 9251e630efdd to make legacy pairing to work doesn't work with
> SC.
>
> Fix by keeping track of what kind of LTK we have, and not distinguishing
> between central/peripheral key slots for SC, which kernel doesn't do and
> AFAIK the role difference doesn't exist in SC.
>
> [...]
Here is the summary with links:
- [BlueZ,1/4] mgmt: Add defines for the long term key types
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=37e483b0687e
- [BlueZ,2/4] device: Remove unused central field from struct ltk_info
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=a82606b8e1f8
- [BlueZ,3/4] device: Fix resolving a coordinated set over Secure Connections
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4d97be27a1fb
- [BlueZ,4/4] test: functional: run CSIP test for Secure Connections & Legacy Pairing
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=c67833ce2ff8
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:[~2026-09-18 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 0:02 [PATCH BlueZ 0/4] device: Fix resolving a coordinated set over Secure Connections Pauli Virtanen
2026-09-18 0:02 ` [PATCH BlueZ 1/4] mgmt: Add defines for the long term key types Pauli Virtanen
2026-09-18 1:58 ` device: Fix resolving a coordinated set over Secure Connections bluez.test.bot
2026-09-18 0:02 ` [PATCH BlueZ 2/4] device: Remove unused central field from struct ltk_info Pauli Virtanen
2026-09-18 0:02 ` [PATCH BlueZ 3/4] device: Fix resolving a coordinated set over Secure Connections Pauli Virtanen
2026-09-18 0:02 ` [PATCH BlueZ 4/4] test: functional: run CSIP test for Secure Connections & Legacy Pairing Pauli Virtanen
2026-09-18 16:30 ` 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=178974904814.1035983.12606949586547695456.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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.