From: patchwork-bot+bluetooth@kernel.org
To: Xiao Yao <xiaokeqinhealth@126.com>
Cc: linux-bluetooth@vger.kernel.org, xiaoyao@rock-chips.com
Subject: Re: [PATCH v2] Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE
Date: Tue, 12 Dec 2023 16:20:25 +0000 [thread overview]
Message-ID: <170239802565.22444.13565680839471776744.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231211162718.1183182-1-xiaokeqinhealth@126.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 12 Dec 2023 00:27:18 +0800 you wrote:
> From: Xiao Yao <xiaoyao@rock-chips.com>
>
> If two Bluetooth devices both support BR/EDR and BLE, and also
> support Secure Connections, then they only need to pair once.
> The LTK generated during the LE pairing process may be converted
> into a BR/EDR link key for BR/EDR transport, and conversely, a
> link key generated during the BR/EDR SSP pairing process can be
> converted into an LTK for LE transport. Hence, the link type of
> the link key and LTK is not fixed, they can be either an LE LINK
> or an ACL LINK.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE
https://git.kernel.org/bluetooth/bluetooth-next/c/d66abc0fbb27
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:[~2023-12-12 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 16:27 [PATCH v2] Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE Xiao Yao
2023-12-11 17:03 ` [v2] " bluez.test.bot
2023-12-12 16:20 ` patchwork-bot+bluetooth [this message]
2024-08-26 21:17 ` [PATCH v2] " 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=170239802565.22444.13565680839471776744.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=xiaokeqinhealth@126.com \
--cc=xiaoyao@rock-chips.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 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.