From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, vlad.pruteanu@nxp.com
Subject: RE: Add support for setting bcode on bcast sink
Date: Thu, 29 Aug 2024 07:56:45 -0700 (PDT) [thread overview]
Message-ID: <66d08c2d.d40a0220.3b471f.1fb7@mx.google.com> (raw)
In-Reply-To: <20240829095206.91150-2-vlad.pruteanu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1561 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=884682
---Test result---
Test Summary:
CheckPatch PASS 3.21 seconds
GitLint PASS 2.12 seconds
BuildEll PASS 27.19 seconds
BluezMake PASS 1750.76 seconds
MakeCheck PASS 13.11 seconds
MakeDistcheck PASS 181.81 seconds
CheckValgrind PASS 255.83 seconds
CheckSmatch WARNING 360.37 seconds
bluezmakeextell PASS 122.20 seconds
IncrementalBuild PASS 12970.89 seconds
ScanBuild PASS 1055.91 seconds
Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/shared/bap.c:288: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:288: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:288:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structures
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-08-29 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 9:51 [PATCH BlueZ v2 0/8] Add support for setting bcode on bcast sink Vlad Pruteanu
2024-08-29 9:51 ` [PATCH BlueZ v2 1/8] doc/media: Add Encryption and BCode fields to QoS property Vlad Pruteanu
2024-08-29 14:56 ` bluez.test.bot [this message]
2024-08-29 9:52 ` [PATCH BlueZ v2 2/8] transport: Make get_bcast_qos return the encryption flag Vlad Pruteanu
2024-08-29 9:52 ` [PATCH BlueZ v2 3/8] gdbus: Add g_dbus_proxy_set_property_dict Vlad Pruteanu
2024-08-29 9:52 ` [PATCH BlueZ v2 4/8] doc/media: Make QoS property readwrite Vlad Pruteanu
2024-08-29 9:52 ` [PATCH BlueZ v2 5/8] transport: Add set_bcast_qos method Vlad Pruteanu
2024-08-29 9:52 ` [PATCH BlueZ v2 6/8] shared/bap: Enable set qos method for BT_BAP_BCAST_SINK stream Vlad Pruteanu
2024-08-29 9:52 ` [PATCH BlueZ v2 7/8] client/player: Prompt the user to enter the bcode Vlad Pruteanu
2024-08-29 9:52 ` [PATCH BlueZ v2 8/8] bap: Refresh qos stored in setup before doing BIG sync Vlad Pruteanu
2024-09-09 16:20 ` [PATCH BlueZ v2 0/8] Add support for setting bcode on bcast sink patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2024-08-22 13:12 [PATCH BlueZ v2 1/8] doc/media: Add Encryption and BCode fields to QoS property Vlad Pruteanu
2024-08-22 18:10 ` Add support for setting bcode on bcast sink bluez.test.bot
2024-08-20 10:39 [PATCH BlueZ 1/8] doc/media: Add Encryption and BCode fields to QoS property Vlad Pruteanu
2024-08-20 15:54 ` Add support for setting bcode on bcast sink 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=66d08c2d.d40a0220.3b471f.1fb7@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vlad.pruteanu@nxp.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