From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1,1/3] btdev: Fix not clearing le_pa_sync_handle on reset
Date: Thu, 25 Jan 2024 07:55:20 -0800 (PST) [thread overview]
Message-ID: <65b28468.170a0220.15fed.66cd@mx.google.com> (raw)
In-Reply-To: <20240125142936.3373953-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1956 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=819897
---Test result---
Test Summary:
CheckPatch PASS 0.93 seconds
GitLint PASS 0.67 seconds
BuildEll PASS 24.08 seconds
BluezMake PASS 724.48 seconds
MakeCheck PASS 11.50 seconds
MakeDistcheck PASS 160.61 seconds
CheckValgrind PASS 226.22 seconds
CheckSmatch WARNING 334.66 seconds
bluezmakeextell PASS 112.05 seconds
IncrementalBuild PASS 2072.65 seconds
ScanBuild WARNING 943.15 seconds
Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
emulator/btdev.c:420:29: warning: Variable length array is used.
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
emulator/btdev.c:1084: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:1335: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:1457: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-01-25 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 14:29 [PATCH BlueZ v1 1/3] btdev: Fix not clearing le_pa_sync_handle on reset Luiz Augusto von Dentz
2024-01-25 14:29 ` [PATCH BlueZ v1 2/3] device: Add btd_device_set_connectable Luiz Augusto von Dentz
2024-01-25 14:29 ` [PATCH BlueZ v1 3/3] bap: Mark device as connectable if a broadcast Endpoint is found Luiz Augusto von Dentz
2024-01-25 15:55 ` bluez.test.bot [this message]
2024-01-25 19:10 ` [PATCH BlueZ v1 1/3] btdev: Fix not clearing le_pa_sync_handle on reset patchwork-bot+bluetooth
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=65b28468.170a0220.15fed.66cd@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.