From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, naga.akella@oss.qualcomm.com
Subject: RE: Add initial Channel Sounding support
Date: Wed, 15 Apr 2026 23:50:16 -0700 (PDT) [thread overview]
Message-ID: <69e086a8.050a0220.190378.3ff0@mx.google.com> (raw)
In-Reply-To: <20260416042012.1204688-2-naga.akella@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 990 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=1081856
---Test result---
Test Summary:
CheckPatch PASS 2.25 seconds
GitLint PASS 0.79 seconds
BuildEll PASS 20.23 seconds
BluezMake PASS 647.34 seconds
MakeCheck PASS 18.75 seconds
MakeDistcheck PASS 244.38 seconds
CheckValgrind PASS 291.23 seconds
CheckSmatch PASS 347.15 seconds
bluezmakeextell PASS 180.71 seconds
IncrementalBuild PASS 690.91 seconds
ScanBuild PASS 1014.28 seconds
https://github.com/bluez/bluez/pull/2043
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-04-16 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 4:20 [PATCH BlueZ v9 0/3] Add initial Channel Sounding support Naga Bhavani Akella
2026-04-16 4:20 ` [PATCH BlueZ v9 1/3] shared: rap: Introduce Channel Sounding HCI raw interface support Naga Bhavani Akella
2026-04-16 6:50 ` bluez.test.bot [this message]
2026-04-16 4:20 ` [PATCH BlueZ v9 2/3] main.conf: Add Channel Sounding config parsing support Naga Bhavani Akella
2026-04-16 4:20 ` [PATCH BlueZ v9 3/3] profiles: ranging: Add HCI LE Event Handling in Reflector role Naga Bhavani Akella
-- strict thread matches above, loose matches on Subject: below --
2026-04-14 15:33 [PATCH BlueZ v6 1/3] shared: rap: Introduce Channel Sounding HCI raw interface support Naga Bhavani Akella
2026-04-14 16:18 ` Add initial Channel Sounding support bluez.test.bot
2026-04-14 18:21 ` bluez.test.bot
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=69e086a8.050a0220.190378.3ff0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox