Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, prathibha.madugonde@oss.qualcomm.com
Subject: RE: Channel Sounding: Aggregate procedure data and expose via D-Bus
Date: Fri, 17 Jul 2026 02:10:52 -0700 (PDT)	[thread overview]
Message-ID: <6a59f19c.d1a89f1f.1cd619.26e3@mx.google.com> (raw)
In-Reply-To: <20260717072647.255002-2-prathm@qti.qualcomm.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.95 seconds
GitLint                       FAIL      0.69 seconds
BuildEll                      PASS      25.67 seconds
BluezMake                     PASS      541.37 seconds
MakeCheck                     PASS      1.04 seconds
MakeDistcheck                 PASS      153.47 seconds
CheckValgrind                 PASS      146.41 seconds
CheckSmatch                   PASS      296.61 seconds
bluezmakeextell               PASS      95.73 seconds
IncrementalBuild              PASS      510.76 seconds
ScanBuild                     PASS      893.79 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v1,1/2] shared/rap: Add bcs_procedure_data aggregation and procedure data API

1: T1 Title exceeds max length (84>80): "[BlueZ,v1,1/2] shared/rap: Add bcs_procedure_data aggregation and procedure data API"
[BlueZ,v1,2/2] profiles/ranging: Add D-Bus ProcedureData signal for Channel Sounding

1: T1 Title exceeds max length (84>80): "[BlueZ,v1,2/2] profiles/ranging: Add D-Bus ProcedureData signal for Channel Sounding"


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

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-07-17  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17  7:26 [PATCH BlueZ v1 0/2] Channel Sounding: Aggregate procedure data and expose via D-Bus Prathibha Madugonde
2026-07-17  7:26 ` [PATCH BlueZ v1 1/2] shared/rap: Add bcs_procedure_data aggregation and procedure data API Prathibha Madugonde
2026-07-17  9:10   ` bluez.test.bot [this message]
2026-07-17  7:26 ` [PATCH BlueZ v1 2/2] profiles/ranging: Add D-Bus ProcedureData signal for Channel Sounding Prathibha Madugonde
2026-07-17 15:07   ` Luiz Augusto von Dentz
2026-07-17 15:17     ` Luiz Augusto von Dentz
2026-07-17 15:44       ` 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=6a59f19c.d1a89f1f.1cd619.26e3@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=prathibha.madugonde@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