From: patchwork-bot+bluetooth@kernel.org
To: Radek Podgorny <radek@podgorny.cz>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
luiz.von.dentz@intel.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: put the peer's on-air address on air when we cannot resolve
Date: Wed, 09 Sep 2026 19:40:07 +0000 [thread overview]
Message-ID: <178898280763.1023805.2181772004585809678.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260908-for-upstream-le-connect-on-air-addr-v2-1-2ae9fa066ec8@podgorny.cz>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 08 Sep 2026 22:41:38 +0200 you wrote:
> An identity address only reaches a peer that is advertising an RPA if the
> controller resolves it on our behalf. Where it cannot, the host has to put
> the peer's on-air address on air itself.
>
> hci_connect_le() still swaps the caller's identity address for the peer's
> cached RPA before creating the connection, but __hci_conn_add() resolves
> the RPA back to the identity address when it stores it, so the identity is
> what goes out. Storing the identity is right when the controller
> translates it on the way to the radio; without LL Privacy, or with this
> peer absent from the resolving list, nothing does.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: put the peer's on-air address on air when we cannot resolve
https://git.kernel.org/bluetooth/bluetooth-next/c/e35544d23359
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-09 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 20:41 Radek Podgorny
2026-09-09 19:40 ` 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=178898280763.1023805.2181772004585809678.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=radek@podgorny.cz \
/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
all inboxes | Powered by JetHome®