From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, michal.dzik@streamunlimited.com
Subject: RE: BAP broadcast fixes
Date: Fri, 17 Apr 2026 03:40:23 -0700 (PDT) [thread overview]
Message-ID: <69e20e17.050a0220.39a7ba.deaa@mx.google.com> (raw)
In-Reply-To: <20260417084809.3633687-3-michal.dzik@streamunlimited.com>
[-- Attachment #1: Type: text/plain, Size: 2691 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=1082418
---Test result---
Test Summary:
CheckPatch FAIL 1.53 seconds
GitLint PASS 1.08 seconds
BuildEll PASS 20.08 seconds
BluezMake PASS 644.28 seconds
MakeCheck PASS 18.64 seconds
MakeDistcheck PASS 243.92 seconds
CheckValgrind PASS 289.61 seconds
CheckSmatch WARNING 345.58 seconds
bluezmakeextell PASS 180.77 seconds
IncrementalBuild PASS 664.51 seconds
ScanBuild PASS 1005.91 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,3/4] audio/bap: fill BIG and BIS for receiver
WARNING:TYPO_SPELLING: 'explicitely' may be misspelled - perhaps 'explicitly'?
#104:
explicitely in BASE, but we can use subgroup index with success.
^^^^^^^^^^^
WARNING:LONG_LINE: line length of 81 exceeds 80 columns
#138: FILE: profiles/audio/bap.c:1556:
+ create_stream_for_bis(data, lpac, sid, bis, sgrp, qos, caps, meta, path);
/github/workspace/src/patch/14528085.patch total: 0 errors, 2 warnings, 23 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/patch/14528085.patch has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
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/2051
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-04-17 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 8:48 [PATCH BlueZ 0/4] BAP broadcast fixes Michal Dzik
2026-04-17 8:48 ` [PATCH BlueZ 1/4] transport: allow setting Metadata property on broadcast Michal Dzik
2026-04-17 10:40 ` bluez.test.bot [this message]
2026-04-17 8:48 ` [PATCH BlueZ 2/4] shared/bap: run callback after setting the broadcast metadata Michal Dzik
2026-04-17 8:48 ` [PATCH BlueZ 3/4] audio/bap: fill BIG and BIS for receiver Michal Dzik
2026-04-17 8:48 ` [PATCH BlueZ 4/4] audio: update QoS dbus property after it is set Michal Dzik
-- strict thread matches above, loose matches on Subject: below --
2026-04-17 11:29 [PATCH BlueZ v2 1/4] transport: allow setting Metadata property on broadcast Michal Dzik
2026-04-17 12:27 ` BAP broadcast fixes 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=69e20e17.050a0220.39a7ba.deaa@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michal.dzik@streamunlimited.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