From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, andrei.istodorescu@nxp.com
Subject: RE: Create transports for matching BISes
Date: Fri, 10 May 2024 09:07:53 -0700 (PDT) [thread overview]
Message-ID: <663e4659.370a0220.f89b8.5df8@mx.google.com> (raw)
In-Reply-To: <20240510133504.26047-2-andrei.istodorescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2363 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=852298
---Test result---
Test Summary:
CheckPatch PASS 2.00 seconds
GitLint PASS 0.67 seconds
BuildEll PASS 24.98 seconds
BluezMake PASS 1732.41 seconds
MakeCheck PASS 12.82 seconds
MakeDistcheck PASS 176.66 seconds
CheckValgrind PASS 246.76 seconds
CheckSmatch WARNING 358.33 seconds
bluezmakeextell PASS 125.08 seconds
IncrementalBuild PASS 3178.06 seconds
ScanBuild WARNING 995.02 seconds
Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/shared/bap.c:285: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:285: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:285: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:285: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:285: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:285:25: warning: array of flexible structuressrc/shared/bap.c: note: in included file:./src/shared/ascs.h:88:25: warning: array of flexible structures
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
src/shared/bap.c:6522:22: warning: Value stored to 'match_data' during its initialization is never read
struct bt_ltv_match match_data = {0};
^~~~~~~~~~ ~~~
1 warning generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-05-10 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 13:35 [PATCH BlueZ 0/2] Create transports for matching BISes Andrei Istodorescu
2024-05-10 13:35 ` [PATCH BlueZ 1/2] shared/bap: Update stream management to avoid PACs Andrei Istodorescu
2024-05-10 16:07 ` bluez.test.bot [this message]
2024-05-10 13:35 ` [PATCH BlueZ 2/2] bap: Create transports for matching BISes Andrei Istodorescu
-- strict thread matches above, loose matches on Subject: below --
2024-05-16 13:03 [PATCH BlueZ v5 1/6] shared/bap: Update stream management to avoid PACs Andrei Istodorescu
2024-05-16 16:53 ` Create transports for matching BISes bluez.test.bot
2024-05-14 11:39 [PATCH BlueZ v4 1/2] shared/bap: Update stream management to avoid PACs Andrei Istodorescu
2024-05-14 14:17 ` Create transports for matching BISes bluez.test.bot
2024-05-13 11:50 [PATCH BlueZ v3 1/2] shared/bap: Update stream management to avoid PACs Andrei Istodorescu
2024-05-13 12:25 ` Create transports for matching BISes bluez.test.bot
2024-04-19 18:07 [PATCH BlueZ 1/5] shared/bap: Allow NULL bap endpoint in streams Andrei Istodorescu
2024-04-19 21:16 ` Create transports for matching BISes 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=663e4659.370a0220.f89b8.5df8@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=andrei.istodorescu@nxp.com \
--cc=linux-bluetooth@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).