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 v2 00/14] Ranging Profile and Ranging Service PTS fixes
Date: Fri, 09 Oct 2026 17:20:06 +0000 [thread overview]
Message-ID: <179156640627.904243.17709722202598866188.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261009092532.3600749-1-cheng.jiang@oss.qualcomm.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 9 Oct 2026 17:25:16 +0800 you wrote:
> Changes since v1, from review:
>
> - src/ and unit/ are in separate patches throughout. Two of those splits
> leave the unit tests broken in between: patch 2 changes gatt_db_notify_t
> and patch 3 updates the test callbacks, so on patch 2 alone they do not
> compile; patch 6 advertises Abort Operation in RAS Features and patch 7
> updates the value test-rap expects. src/bluetoothd builds on every patch,
> and the tests pass once each pair is applied. Squashing the pairs would
> avoid it, if you would rather have that.
>
> [...]
Here is the summary with links:
- [v2,01/14] shared/gatt-client: Allow registering notify with explicit CCC value
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=52fdca35b8e7
- [v2,02/14] shared/gatt-db: Pass the ATT opcode to the notify callback
(no matching commit)
- [v2,03/14] unit: Take the ATT opcode in the notify callbacks
(no matching commit)
- [v2,04/14] shared/gatt-db: Add gatt_db_attribute_indicate()
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8199d710021e
- [v2,05/14] shared/rap: Honor CCCD transport for RAS on-demand ranging data
(no matching commit)
- [v2,06/14] shared/rap: Add RAS Control Point Abort Operation
(no matching commit)
- [v2,07/14] unit/test-rap: Expect Abort Operation in RAS Features
(no matching commit)
- [v2,08/14] shared/rap: Shorten the requester Control Point response timeout
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=bf0ce0541f28
- [v2,09/14] shared/rap: Add real-time ranging data delivery on the responder
(no matching commit)
- [v2,10/14] shared/rap: Add requester ranging data subscription API
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=14ad98fba11c
- [v2,11/14] profiles/ranging: Expose requester ranging data mode over D-Bus
(no matching commit)
- [v2,12/14] client: Add Channel Sounding ranging data mode control
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=68ac6ad752f2
- [v2,13/14] doc: Document Channel Sounding ranging data mode control
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=2cd5045f1ec4
- [v2,14/14] doc/qualification: Add RAP/RAS PTS qualification results
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b111351fd617
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-10-09 17:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 9:25 [PATCH v2 00/14] Ranging Profile and Ranging Service PTS fixes Cheng Jiang
2026-10-09 9:25 ` [PATCH v2 01/14] shared/gatt-client: Allow registering notify with explicit CCC value Cheng Jiang
2026-10-09 15:42 ` Ranging Profile and Ranging Service PTS fixes bluez.test.bot
2026-10-09 9:25 ` [PATCH v2 02/14] shared/gatt-db: Pass the ATT opcode to the notify callback Cheng Jiang
2026-10-09 9:25 ` [PATCH v2 03/14] unit: Take the ATT opcode in the notify callbacks Cheng Jiang
2026-10-09 9:25 ` [PATCH v2 04/14] shared/gatt-db: Add gatt_db_attribute_indicate() Cheng Jiang
2026-10-09 9:25 ` [PATCH v2 05/14] shared/rap: Honor CCCD transport for RAS on-demand ranging data Cheng Jiang
2026-10-09 9:25 ` [PATCH v2 06/14] shared/rap: Add RAS Control Point Abort Operation Cheng Jiang
2026-10-09 9:25 ` [PATCH v2 07/14] unit/test-rap: Expect Abort Operation in RAS Features Cheng Jiang
2026-10-09 9:25 ` [PATCH v2 08/14] shared/rap: Shorten the requester Control Point response timeout Cheng Jiang
2026-10-09 9:25 ` [PATCH v2 09/14] shared/rap: Add real-time ranging data delivery on the responder Cheng Jiang
2026-10-09 9:25 ` [PATCH v2 10/14] shared/rap: Add requester ranging data subscription API Cheng Jiang
2026-10-09 9:25 ` [PATCH v2 11/14] profiles/ranging: Expose requester ranging data mode over D-Bus Cheng Jiang
2026-10-09 9:25 ` [PATCH v2 12/14] client: Add Channel Sounding ranging data mode control Cheng Jiang
2026-10-09 9:25 ` [PATCH v2 13/14] doc: Document " Cheng Jiang
2026-10-09 9:25 ` [PATCH v2 14/14] doc/qualification: Add RAP/RAS PTS qualification results Cheng Jiang
2026-10-09 17:20 ` 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=179156640627.904243.17709722202598866188.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