From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, brian.gix@intel.com
Subject: RE: Mesh demon switched to using kernel Mesh MGMT
Date: Thu, 22 Sep 2022 16:26:52 -0700 (PDT) [thread overview]
Message-ID: <632cef3c.050a0220.70b6e.306d@mx.google.com> (raw)
In-Reply-To: <20220922223102.640173-2-brian.gix@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1698 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=679632
---Test result---
Test Summary:
CheckPatch PASS 4.12 seconds
GitLint PASS 2.16 seconds
Prep - Setup ELL PASS 26.03 seconds
Build - Prep PASS 0.78 seconds
Build - Configure PASS 8.19 seconds
Build - Make PASS 719.47 seconds
Make Check PASS 11.86 seconds
Make Check w/Valgrind PASS 287.40 seconds
Make Distcheck PASS 237.01 seconds
Build w/ext ELL - Configure PASS 8.28 seconds
Build w/ext ELL - Make PASS 83.69 seconds
Incremental Build w/ patches PASS 197.42 seconds
Scan Build WARNING 523.64 seconds
Details
##############################
Test: Scan Build - WARNING
Desc: Run Scan Build with patches
Output:
*****************************************************************************
The bugs reported by the scan-build may or may not be caused by your patches.
Please check the list and fix the bugs if they are caused by your patch.
*****************************************************************************
mesh/mesh-io.c:118:18: warning: Access to field 'rx_regs' results in a dereference of a null pointer (loaded from variable 'io')
l_queue_destroy(io->rx_regs, l_free);
^~~~~~~~~~~
1 warning generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-09-22 23:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 22:31 [PATCH BlueZ v4 0/2] Mesh demon switched to using kernel Mesh MGMT Brian Gix
2022-09-22 22:31 ` [PATCH BlueZ v4 1/2] mesh: Improve PB-ADV timing for reliability Brian Gix
2022-09-22 23:26 ` bluez.test.bot [this message]
2022-09-22 22:31 ` [PATCH BlueZ v4 2/2] mesh: Add new kernel MGMT based IO transport Brian Gix
-- strict thread matches above, loose matches on Subject: below --
2022-09-23 18:00 [PATCH BlueZ v5 1/2] mesh: Improve PB-ADV timing for reliability Brian Gix
2022-09-23 19:24 ` Mesh demon switched to using kernel Mesh MGMT bluez.test.bot
2022-09-22 21:40 [PATCH BlueZ v3 1/2] mesh: Improve PB-ADV timing for reliability Brian Gix
2022-09-22 22:26 ` Mesh demon switched to using kernel Mesh MGMT bluez.test.bot
2022-09-22 21:38 [PATCH BlueZ v2 1/2] mesh: Improve PB-ADV timing for reliability Brian Gix
2022-09-22 22:24 ` Mesh demon switched to using kernel Mesh MGMT bluez.test.bot
2022-09-22 20:38 [PATCH BlueZ 1/4] mgmt: Add support for Mesh in the kernel Brian Gix
2022-09-22 21:32 ` Mesh demon switched to using kernel Mesh MGMT 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=632cef3c.050a0220.70b6e.306d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=brian.gix@intel.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