public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, naga.akella@oss.qualcomm.com
Subject: RE: Add initial Channel Sounding support for
Date: Tue, 21 Apr 2026 05:48:18 -0700 (PDT)	[thread overview]
Message-ID: <69e77212.d40a0220.3d709c.9dc5@mx.google.com> (raw)
In-Reply-To: <20260421113148.3809176-2-naga.akella@oss.qualcomm.com>

[-- Attachment #1: Type: text/plain, Size: 1802 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=1083806

---Test result---

Test Summary:
CheckPatch                    PASS      2.60 seconds
GitLint                       FAIL      1.03 seconds
BuildEll                      PASS      20.01 seconds
BluezMake                     PASS      642.15 seconds
MakeCheck                     PASS      18.68 seconds
MakeDistcheck                 PASS      244.26 seconds
CheckValgrind                 PASS      291.29 seconds
CheckSmatch                   WARNING   346.14 seconds
bluezmakeextell               PASS      181.46 seconds
IncrementalBuild              PASS      687.56 seconds
ScanBuild                     PASS      996.61 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v11,1/3] shared: rap: Introduce Channel Sounding HCI raw interface support

WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
1: T1 Title exceeds max length (81>80): "[BlueZ,v11,1/3] shared: rap: Introduce Channel Sounding HCI raw interface support"
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/main.c: note: in included file (through src/device.h):


https://github.com/bluez/bluez/pull/2059

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-04-21 12:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 11:31 [PATCH BlueZ v11 0/3] Add initial Channel Sounding support for Naga Bhavani Akella
2026-04-21 11:31 ` [PATCH BlueZ v11 1/3] shared: rap: Introduce Channel Sounding HCI raw interface support Naga Bhavani Akella
2026-04-21 12:48   ` bluez.test.bot [this message]
2026-04-21 11:31 ` [PATCH BlueZ v11 2/3] main.conf: Add Channel Sounding config parsing support Naga Bhavani Akella
2026-04-21 11:31 ` [PATCH BlueZ v11 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-17 13:56 [PATCH BlueZ v10 1/3] shared: rap: Introduce Channel Sounding HCI raw interface support Naga Bhavani Akella
2026-04-17 15:41 ` Add initial Channel Sounding support for 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=69e77212.d40a0220.3d709c.9dc5@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