From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, cheng.jiang@oss.qualcomm.com
Subject: RE: Channel Sounding and RAP fixes
Date: Mon, 02 Nov 2026 01:08:04 -0800 (PST) [thread overview]
Message-ID: <6ae852f4.d643d4e7.f723c.a651@mx.google.com> (raw)
In-Reply-To: <20261102081913.1623864-2-cheng.jiang@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1736 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/series/1198568/
---Test result---
Test Summary:
CheckPatch PASS 7.35 seconds
GitLint FAIL 4.51 seconds
BuildEll PASS 13.67 seconds
BluezMake PASS 179.90 seconds
MakeCheck PASS 13.01 seconds
MakeDistcheck PASS 99.32 seconds
CheckValgrind PASS 157.65 seconds
CheckSmatch PASS 179.66 seconds
bluezmakeextell PASS 63.53 seconds
TestFunctional PASS 845.97 seconds
IncrementalBuild PASS 317.45 seconds
ScanBuild PASS 637.91 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,08/15] profiles/ranging: Let StartMeasurement() pick the Initiator for Both
1: T1 Title exceeds max length (82>80): "[BlueZ,08/15] profiles/ranging: Let StartMeasurement() pick the Initiator for Both"
[BlueZ,12/15] profiles/ranging: Defer CS Security Enable until the link is encrypted
1: T1 Title exceeds max length (84>80): "[BlueZ,12/15] profiles/ranging: Defer CS Security Enable until the link is encrypted"
[BlueZ,13/15] profiles/ranging: Choose the CS antenna configuration from both ends
1: T1 Title exceeds max length (82>80): "[BlueZ,13/15] profiles/ranging: Choose the CS antenna configuration from both ends"
https://github.com/bluez/bluez/pull/2747
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-02 9:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 8:18 [PATCH BlueZ 00/15] Channel Sounding and RAP fixes Cheng Jiang
2026-11-02 8:18 ` [PATCH BlueZ 01/15] gatt-database: Drop stale device state for removed bonds Cheng Jiang
2026-11-02 9:08 ` bluez.test.bot [this message]
2026-11-02 8:18 ` [PATCH BlueZ 02/15] shared/rap: Reset the readable Ranging Counters per connection Cheng Jiang
2026-11-02 8:19 ` [PATCH BlueZ 03/15] shared/rap: Subscribe on-demand data with the requested transport Cheng Jiang
2026-11-02 8:19 ` [PATCH BlueZ 04/15] shared/rap: Subscribe to Ranging Data when a measurement starts Cheng Jiang
2026-11-02 8:19 ` [PATCH BlueZ 05/15] client/cs: Fix use-after-free in stop_measurement_reply Cheng Jiang
2026-11-02 8:19 ` [PATCH BlueZ 06/15] shared/hci: Look up the connection handle on the right link Cheng Jiang
2026-11-02 8:19 ` [PATCH BlueZ 07/15] profiles/ranging: Let the Reflector run the CS setup phase Cheng Jiang
2026-11-02 8:19 ` [PATCH BlueZ 08/15] profiles/ranging: Let StartMeasurement() pick the Initiator for Both Cheng Jiang
2026-11-02 8:19 ` [PATCH BlueZ 09/15] profiles/ranging: Take the CS role from Config Complete Cheng Jiang
2026-11-02 8:19 ` [PATCH BlueZ 10/15] profiles/ranging: Act on a CS configuration created by the peer Cheng Jiang
2026-11-02 8:19 ` [PATCH BlueZ 11/15] profiles/ranging: Keep a peer-driven setup from being rewound Cheng Jiang
2026-11-02 8:19 ` [PATCH BlueZ 12/15] profiles/ranging: Defer CS Security Enable until the link is encrypted Cheng Jiang
2026-11-02 8:19 ` [PATCH BlueZ 13/15] profiles/ranging: Choose the CS antenna configuration from both ends Cheng Jiang
2026-11-02 8:19 ` [PATCH BlueZ 14/15] profiles/ranging: Do not start a procedure after StopMeasurement() Cheng Jiang
2026-11-02 8:19 ` [PATCH BlueZ 15/15] shared/rap: Start the Real-time timeout when the procedure starts Cheng Jiang
2026-11-03 20:38 ` [PATCH BlueZ 00/15] Channel Sounding and RAP fixes Luiz Augusto von Dentz
2026-11-04 3:04 ` Cheng Jiang
2026-11-04 15:07 ` 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=6ae852f4.d643d4e7.f723c.a651@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
/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