From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ceggers@arri.de
Subject: RE: properties_changed: check for NULL iterator
Date: Fri, 23 Sep 2022 04:21:54 -0700 (PDT) [thread overview]
Message-ID: <632d96d2.050a0220.966ee.3608@mx.google.com> (raw)
In-Reply-To: <20220923102421.10336-2-ceggers@arri.de>
[-- Attachment #1: Type: text/plain, Size: 1995 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=679824
---Test result---
Test Summary:
CheckPatch PASS 12.59 seconds
GitLint FAIL 8.83 seconds
Prep - Setup ELL PASS 26.35 seconds
Build - Prep PASS 0.79 seconds
Build - Configure PASS 8.36 seconds
Build - Make PASS 747.77 seconds
Make Check PASS 11.00 seconds
Make Check w/Valgrind PASS 289.46 seconds
Make Distcheck PASS 239.58 seconds
Build w/ext ELL - Configure PASS 8.42 seconds
Build w/ext ELL - Make PASS 84.11 seconds
Incremental Build w/ patches PASS 892.46 seconds
Scan Build WARNING 493.39 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
[BlueZ,9/9] battery: provided_battery_property_changed_cb: check for NULL iterator
1: T1 Title exceeds max length (82>80): "[BlueZ,9/9] battery: provided_battery_property_changed_cb: check for NULL iterator"
##############################
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.
*****************************************************************************
client/gatt.c:2146:2: warning: Null pointer passed to 2nd parameter expecting 'nonnull'
memcpy(*dst_value + offset, src_val, src_len);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-09-23 11:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 10:24 [PATCH BlueZ 0/9] properties_changed: check for NULL iterator Christian Eggers
2022-09-23 10:24 ` [PATCH BlueZ 1/9] advertising: parse_secondary: fix loop condition Christian Eggers
2022-09-23 11:21 ` bluez.test.bot [this message]
2022-09-23 10:24 ` [PATCH BlueZ 2/9] advertising: parse_secondary: fix mask value Christian Eggers
2022-09-23 10:24 ` [PATCH BlueZ 3/9] advertising: parse_secondary: check for NULL iterator Christian Eggers
2022-09-23 10:24 ` [PATCH BlueZ 4/9] advertising: parse_min_interval: reset min_interval if iter is NULL Christian Eggers
2022-09-23 10:26 ` Christian Eggers
2022-09-23 20:50 ` patchwork-bot+bluetooth
2022-09-23 10:26 ` [PATCH BlueZ 5/9] advertising: parse_[min|max]_interval: reset value " Christian Eggers
2022-09-23 10:26 ` [PATCH BlueZ 6/9] advertising: parse_tx_power: " Christian Eggers
2022-09-23 10:26 ` [PATCH BlueZ 7/9] client/gatt: proxy_property_changed: check for NULL iterator Christian Eggers
2022-09-23 10:27 ` [PATCH BlueZ 8/9] gatt: " Christian Eggers
2022-09-23 10:27 ` [PATCH BlueZ 9/9] battery: provided_battery_property_changed_cb: " Christian Eggers
2022-09-23 14:55 [PATCH BlueZ v2 1/9] advertising: parse_secondary: fix loop condition Christian Eggers
2022-09-23 15:47 ` properties_changed: check for NULL iterator bluez.test.bot
2022-09-29 16:49 ` bluez.test.bot
2022-09-29 17:45 ` bluez.test.bot
2022-09-29 18:40 ` bluez.test.bot
2022-09-29 19:01 ` bluez.test.bot
2022-09-29 19:29 ` bluez.test.bot
2022-09-29 19:47 ` bluez.test.bot
2022-09-29 20:34 ` bluez.test.bot
2022-09-29 20:53 ` bluez.test.bot
2022-09-29 21:30 ` bluez.test.bot
2022-09-29 21:52 ` bluez.test.bot
2022-09-29 22:32 ` bluez.test.bot
2022-09-29 22:52 ` bluez.test.bot
2022-09-29 23:40 ` bluez.test.bot
2022-09-29 23:59 ` 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=632d96d2.050a0220.966ee.3608@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=ceggers@arri.de \
--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 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.