public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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 05:27:11 -0700 (PDT)	[thread overview]
Message-ID: <69e2271f.050a0220.94ee0.6c54@mx.google.com> (raw)
In-Reply-To: <20260417112914.3752605-2-michal.dzik@streamunlimited.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=1082491

---Test result---

Test Summary:
CheckPatch                    PASS      1.23 seconds
GitLint                       PASS      0.86 seconds
BuildEll                      PASS      17.39 seconds
BluezMake                     PASS      598.33 seconds
MakeCheck                     PASS      18.56 seconds
MakeDistcheck                 PASS      216.71 seconds
CheckValgrind                 PASS      272.46 seconds
CheckSmatch                   WARNING   305.10 seconds
bluezmakeextell               PASS      163.38 seconds
IncrementalBuild              PASS      621.83 seconds
ScanBuild                     PASS      901.92 seconds

Details
##############################
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/2052

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-04-17 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17 11:29 [PATCH BlueZ v2 0/4] BAP broadcast fixes Michal Dzik
2026-04-17 11:29 ` [PATCH BlueZ v2 1/4] transport: allow setting Metadata property on broadcast Michal Dzik
2026-04-17 12:27   ` bluez.test.bot [this message]
2026-04-17 11:29 ` [PATCH BlueZ v2 2/4] shared/bap: run callback after setting the broadcast metadata Michal Dzik
2026-04-17 11:29 ` [PATCH BlueZ v2 3/4] audio/bap: fill BIG and BIS for receiver Michal Dzik
2026-04-17 11:29 ` [PATCH BlueZ v2 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  8:48 [PATCH BlueZ 1/4] transport: allow setting Metadata property on broadcast Michal Dzik
2026-04-17 10:40 ` 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=69e2271f.050a0220.94ee0.6c54@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