From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: iso-tester: Add tests for Broadcast Receiver sync to 2 BIGs
Date: Fri, 01 Nov 2024 08:47:14 -0700 (PDT) [thread overview]
Message-ID: <6724f802.170a0220.17313b.cae0@mx.google.com> (raw)
In-Reply-To: <20241101115118.43891-2-iulia.tanasescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2022 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=905388
---Test result---
Test Summary:
CheckPatch PASS 1.62 seconds
GitLint PASS 0.95 seconds
BuildEll PASS 24.64 seconds
BluezMake PASS 1641.57 seconds
MakeCheck PASS 12.98 seconds
MakeDistcheck PASS 179.56 seconds
CheckValgrind PASS 254.58 seconds
CheckSmatch WARNING 358.27 seconds
bluezmakeextell PASS 120.52 seconds
IncrementalBuild PASS 8125.02 seconds
ScanBuild WARNING 1010.64 seconds
Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
emulator/btdev.c:448:29: warning: Variable length array is used.emulator/btdev.c:448:29: warning: Variable length array is used.
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
emulator/btdev.c:1122:10: warning: Although the value stored to 'conn' is used in the enclosing expression, the value is never actually read from 'conn'
while ((conn = queue_find(dev->conns, match_handle,
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
emulator/btdev.c:1409:24: warning: Access to field 'link' results in a dereference of a null pointer (loaded from variable 'conn')
pending_conn_del(dev, conn->link->dev);
^~~~~~~~~~
emulator/btdev.c:1531:13: warning: Access to field 'dev' results in a dereference of a null pointer (loaded from variable 'conn')
send_event(conn->dev, BT_HCI_EVT_AUTH_COMPLETE, &ev, sizeof(ev));
^~~~~~~~~
3 warnings generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-11-01 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 11:51 [PATCH BlueZ v2 0/5] iso-tester: Add tests for Broadcast Receiver sync to 2 BIGs Iulia Tanasescu
2024-11-01 11:51 ` [PATCH BlueZ v2 1/5] btdev: Add support for syncing to multiple PA trains Iulia Tanasescu
2024-11-01 15:47 ` bluez.test.bot [this message]
2024-11-01 11:51 ` [PATCH BlueZ v2 2/5] btdev: Add support for syncing to multiple BIGs Iulia Tanasescu
2024-11-01 11:51 ` [PATCH BlueZ v2 3/5] iso-tester: Fix memory leaks in iso_accept_cb Iulia Tanasescu
2024-11-01 11:51 ` [PATCH BlueZ v2 4/5] iso-tester: Add test for Broadcast Receiver sync to 2 BIGs Iulia Tanasescu
2024-11-01 11:51 ` [PATCH BlueZ v2 5/5] iso-tester: Add test for Broadcast Receiver Defer " Iulia Tanasescu
2024-11-05 14:20 ` [PATCH BlueZ v2 0/5] iso-tester: Add tests for Broadcast Receiver " patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2024-11-01 8:31 [PATCH BlueZ 1/5] btdev: Add support for syncing to multiple PA trains Iulia Tanasescu
2024-11-01 10:06 ` iso-tester: Add tests for Broadcast Receiver sync to 2 BIGs 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=6724f802.170a0220.17313b.cae0@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=iulia.tanasescu@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 NNTP newsgroup(s).