From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: BAP ASE state handling enhancements
Date: Tue, 03 Nov 2026 14:51:18 -0800 (PST) [thread overview]
Message-ID: <6aea6566.54e42a5c.246e68.5497@mx.google.com> (raw)
In-Reply-To: <20261103203011.3904290-2-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2134 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/series/1200848/
---Test result---
Test Summary:
CheckPatch PASS 2.89 seconds
GitLint PASS 1.67 seconds
BuildEll PASS 21.48 seconds
BluezMake PASS 313.38 seconds
MakeCheck PASS 21.60 seconds
MakeDistcheck PASS 154.84 seconds
CheckValgrind PASS 365.43 seconds
CheckSmatch WARNING 302.51 seconds
bluezmakeextell PASS 99.97 seconds
TestFunctional PASS 1236.54 seconds
IncrementalBuild PASS 626.74 seconds
ScanBuild PASS 1200.75 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 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 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/2754
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-03 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 20:30 [PATCH BlueZ v1 0/7] BAP ASE state handling enhancements Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 1/7] shared/bap: Defer ASE state notifications until idle Luiz Augusto von Dentz
2026-11-03 22:51 ` bluez.test.bot [this message]
2026-11-03 20:30 ` [PATCH BlueZ v1 2/7] shared/bap: Wait for ASE state before completing requests Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 3/7] unit/test-bap: Add tests for cancelling grouped Enable Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 4/7] unit/test-bap: Add Notify Multiple test Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 5/7] shared/tester: Add support for alternative PDUs Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 6/7] unit/test-bap: Expect the ASE state following Releasing Luiz Augusto von Dentz
2026-11-03 20:30 ` [PATCH BlueZ v1 7/7] unit/test-bap: Run unicast tests with Notify Multiple 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=6aea6566.54e42a5c.246e68.5497@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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