From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, i.iskakov@omp.ru
Subject: RE: Fix bugs found by static analysis
Date: Wed, 09 Jul 2025 08:11:41 -0700 (PDT) [thread overview]
Message-ID: <686e86ad.050a0220.6a558.5bba@mx.google.com> (raw)
In-Reply-To: <20250709133622.2819849-2-i.iskakov@omp.ru>
[-- Attachment #1: Type: text/plain, Size: 1864 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=980540
---Test result---
Test Summary:
CheckPatch PENDING 0.27 seconds
GitLint PENDING 0.29 seconds
BuildEll PASS 22.59 seconds
BluezMake PASS 2749.28 seconds
MakeCheck PASS 20.24 seconds
MakeDistcheck PASS 189.54 seconds
CheckValgrind PASS 241.91 seconds
CheckSmatch WARNING 315.40 seconds
bluezmakeextell PASS 130.05 seconds
IncrementalBuild PENDING 0.32 seconds
ScanBuild PASS 909.24 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
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 structures
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-07-09 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 13:36 [PATCH BlueZ v4 0/4] Fix bugs found by static analysis Ismagil Iskakov
2025-07-09 13:36 ` [PATCH BlueZ v4 1/4] btio: fix range validation of security level Ismagil Iskakov
2025-07-09 15:11 ` bluez.test.bot [this message]
2025-07-09 13:36 ` [PATCH BlueZ v4 2/4] profiles/audio: add nullity checks Ismagil Iskakov
2025-07-09 13:36 ` [PATCH BlueZ v4 3/4] src/shared: " Ismagil Iskakov
2025-07-09 13:36 ` [PATCH BlueZ v4 4/4] obexd/client: fix err condition causing memleak Ismagil Iskakov
2025-07-09 14:00 ` [PATCH BlueZ v4 0/4] Fix bugs found by static analysis patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2025-07-09 12:18 [PATCH BlueZ v3 1/4] btio: fix range validation of security level Ismagil Iskakov
2025-07-09 13:40 ` Fix bugs found by static analysis bluez.test.bot
2025-07-08 11:08 [PATCH BlueZ v2 01/11] btio: fix range validation of security level Ismagil Iskakov
2025-07-08 12:44 ` Fix bugs found by static analysis bluez.test.bot
2025-07-08 7:33 [PATCH BlueZ 01/11] btio: fix range validation of security level Ismagil Iskakov
2025-07-08 7:51 ` Fix bugs found by static analysis 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=686e86ad.050a0220.6a558.5bba@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=i.iskakov@omp.ru \
--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