From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, raghavendra.rao@collabora.com
Subject: RE: shared/bap: add ASE Control Point error responses
Date: Thu, 04 Jun 2026 02:02:36 -0700 (PDT) [thread overview]
Message-ID: <6a213f2c.0c039065.e7a4.8ca3@mx.google.com> (raw)
In-Reply-To: <20260604052052.10667-2-raghavendra.rao@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 1600 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=1105699
---Test result---
Test Summary:
CheckPatch PASS 0.57 seconds
GitLint PASS 0.33 seconds
BuildEll PASS 20.05 seconds
BluezMake PASS 612.41 seconds
MakeCheck PASS 19.18 seconds
MakeDistcheck PASS 234.26 seconds
CheckValgrind PASS 274.34 seconds
CheckSmatch WARNING 322.83 seconds
bluezmakeextell PASS 165.13 seconds
IncrementalBuild PASS 609.37 seconds
ScanBuild PASS 919.20 seconds
Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/shared/bap.c:317: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:317: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:317: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/2174
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-06-04 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 8:29 [BlueZ PATCH 0/1] shared/bap: add ASE Control Point error responses raghu447
2026-06-02 8:29 ` [BlueZ PATCH 1/1] " raghu447
2026-06-02 11:51 ` bluez.test.bot
2026-06-02 15:01 ` [BlueZ PATCH 1/1] " Luiz Augusto von Dentz
2026-06-04 5:20 ` [BlueZ PATCH v2 0/1] " raghu447
2026-06-04 5:20 ` [BlueZ PATCH v2 1/1] " raghu447
2026-06-04 9:02 ` bluez.test.bot [this message]
2026-06-04 14:56 ` Luiz Augusto von Dentz
2026-06-09 10:25 ` [BlueZ PATCH v3 0/2] " raghu447
2026-06-09 10:25 ` [BlueZ PATCH v3 1/2] " raghu447
2026-06-09 12:48 ` bluez.test.bot
2026-06-09 10:25 ` [BlueZ PATCH v3 2/2] unit/bap: add SPE tests raghu447
2026-06-09 15:20 ` [BlueZ PATCH v3 0/2] shared/bap: add ASE Control Point error responses patchwork-bot+bluetooth
2026-06-02 14:53 ` [BlueZ PATCH 0/1] " 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=6a213f2c.0c039065.e7a4.8ca3@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=raghavendra.rao@collabora.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