From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, naga.akella@oss.qualcomm.com
Subject: RE: client/cs: fix crash in reference ranging provider
Date: Thu, 03 Sep 2026 05:07:24 -0700 (PDT) [thread overview]
Message-ID: <6a9962fc.9385382e.2ee0e2.97e1@mx.google.com> (raw)
In-Reply-To: <20260903101635.3370149-2-naga.akella@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1285 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/project/bluetooth/list/?series=1156962
---Test result---
Test Summary:
CheckPatch PASS 0.55 seconds
GitLint FAIL 0.45 seconds
BuildEll PASS 21.03 seconds
BluezMake PASS 612.71 seconds
MakeCheck PASS 19.36 seconds
MakeDistcheck PASS 168.36 seconds
CheckValgrind PASS 238.29 seconds
CheckSmatch PASS 325.89 seconds
bluezmakeextell PASS 106.60 seconds
IncrementalBuild PASS 610.56 seconds
ScanBuild PASS 1034.59 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v1,1/2] client: avoid registering ranging objects as direct children of "/"
1: T1 Title exceeds max length (82>80): "[BlueZ,v1,1/2] client: avoid registering ranging objects as direct children of "/""
https://github.com/bluez/bluez/pull/2479
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-03 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 10:16 [PATCH BlueZ v1 0/2] client/cs: fix crash in reference ranging provider Naga Bhavani Akella
2026-09-03 10:16 ` [PATCH BlueZ v1 1/2] client: avoid registering ranging objects as direct children of "/" Naga Bhavani Akella
2026-09-03 12:07 ` bluez.test.bot [this message]
2026-09-03 10:16 ` [PATCH BlueZ v1 2/2] doc: note RangingProvider1 objects are nested in bluetoothctl-cs Naga Bhavani Akella
2026-09-08 19:20 ` [PATCH BlueZ v1 0/2] client/cs: fix crash in reference ranging provider patchwork-bot+bluetooth
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=6a9962fc.9385382e.2ee0e2.97e1@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=naga.akella@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 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.