From: patchwork-bot+bluetooth@kernel.org
To: Cheng Jiang <cheng.jiang@oss.qualcomm.com>
Cc: linux-bluetooth@vger.kernel.org, jinwang.li@oss.qualcomm.com,
wei.deng@oss.qualcomm.com, xiuzhuo.shang@oss.qualcomm.com,
shuai.zhang@oss.qualcomm.com
Subject: Re: [PATCH] ranging: Route CS subevent results by connection and configuration
Date: Wed, 30 Sep 2026 15:40:09 +0000 [thread overview]
Message-ID: <179078280977.1986714.4946356790271946414.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260930054528.2258948-1-cheng.jiang@oss.qualcomm.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 30 Sep 2026 13:45:28 +0800 you wrote:
> bt_rap_attach_hci() allocates a state machine per device and registers the
> CS subevent handlers of each one on the shared bt_hci. LE Meta subevents
> are dispatched with queue_foreach() over every registered handler, so each
> CS Subevent Result is delivered to all of them, not only to the device the
> event belongs to.
>
> The Subevent Result and Subevent Result Continue handlers then passed their
> own sm->rap on without checking which connection reported the event, unlike
> every other handler in rap_hci.c, which resolves it with
> find_mapping_by_handle() and returns when the connection is not its own.
> The Connection_Handle was parsed into the event and never read again, in
> rap_hci.c or in shared/rap.c.
>
> [...]
Here is the summary with links:
- ranging: Route CS subevent results by connection and configuration
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=05870ea62923
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-30 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 5:45 [PATCH] ranging: Route CS subevent results by connection and configuration Cheng Jiang
2026-09-30 8:33 ` bluez.test.bot
2026-09-30 15: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=179078280977.1986714.4946356790271946414.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=jinwang.li@oss.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=shuai.zhang@oss.qualcomm.com \
--cc=wei.deng@oss.qualcomm.com \
--cc=xiuzhuo.shang@oss.qualcomm.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