From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kx960506@163.com
Subject: RE: [BlueZ,1/2] shared/bap: Fix unused value in qos
Date: Wed, 20 May 2026 23:44:38 -0700 (PDT) [thread overview]
Message-ID: <6a0ea9d6.9731324b.151088.3f40@mx.google.com> (raw)
In-Reply-To: <20260521032815.1845-1-kx960506@163.com>
[-- Attachment #1: Type: text/plain, Size: 2591 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=1098419
---Test result---
Test Summary:
CheckPatch PASS 0.66 seconds
GitLint FAIL 0.50 seconds
BuildEll PASS 18.04 seconds
BluezMake PASS 643.58 seconds
MakeCheck PASS 14.71 seconds
MakeDistcheck FAIL 213.39 seconds
CheckValgrind PASS 258.46 seconds
CheckSmatch WARNING 313.93 seconds
bluezmakeextell PASS 169.78 seconds
IncrementalBuild PASS 643.36 seconds
ScanBuild PASS 945.89 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,2/2] transport: Add support for obtaining PresentationDelay in broadcast QoS
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 (83>80): "[BlueZ,2/2] transport: Add support for obtaining PresentationDelay in broadcast QoS"
##############################
Test: MakeDistcheck - FAIL
Desc: Run Bluez Make Distcheck
Output:
make[4]: *** [Makefile:10239: test-suite.log] Error 1
make[3]: *** [Makefile:10347: check-TESTS] Error 2
make[2]: *** [Makefile:10818: check-am] Error 2
make[1]: *** [Makefile:10820: check] Error 2
make: *** [Makefile:10741: distcheck] Error 1
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/shared/bap.c:312:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structuressrc/shared/bap.c:312:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structuressrc/shared/bap.c:312:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structures
https://github.com/bluez/bluez/pull/2139
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-05-21 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 3:28 [PATCH BlueZ 1/2] shared/bap: Fix unused value in qos michael_kong
2026-05-21 3:28 ` [PATCH BlueZ 2/2] transport: Add support for obtaining PresentationDelay in broadcast QoS michael_kong
2026-05-21 6:44 ` bluez.test.bot [this message]
2026-05-21 13:40 ` [PATCH BlueZ 1/2] shared/bap: Fix unused value in qos 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=6a0ea9d6.9731324b.151088.3f40@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=kx960506@163.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