From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/2] gatt-api: Add error code ReadValue/WriteValue
Date: Thu, 25 Aug 2022 14:09:01 -0700 (PDT) [thread overview]
Message-ID: <6307e4ed.050a0220.cbc81.04b4@mx.google.com> (raw)
In-Reply-To: <20220825200758.1645136-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2160 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=671211
---Test result---
Test Summary:
CheckPatch PASS 2.27 seconds
GitLint PASS 1.61 seconds
Prep - Setup ELL PASS 26.73 seconds
Build - Prep PASS 0.73 seconds
Build - Configure PASS 8.39 seconds
Build - Make PASS 969.49 seconds
Make Check PASS 11.87 seconds
Make Check w/Valgrind PASS 286.82 seconds
Make Distcheck PASS 235.16 seconds
Build w/ext ELL - Configure PASS 8.64 seconds
Build w/ext ELL - Make PASS 82.00 seconds
Incremental Build w/ patches PASS 194.44 seconds
Scan Build WARNING 491.96 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.
*****************************************************************************
src/gatt-database.c:1138:10: warning: Value stored to 'bits' during its initialization is never read
uint8_t bits[] = { BT_GATT_CHRC_CLI_FEAT_ROBUST_CACHING,
^~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/gatt-database.c:3535:14: warning: Value stored to 'iface' during its initialization is never read
const char *iface = g_dbus_proxy_get_interface(proxy);
^~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/gatt-database.c:3536:14: warning: Value stored to 'path' during its initialization is never read
const char *path = g_dbus_proxy_get_path(proxy);
^~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3 warnings generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-08-25 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 20:07 [PATCH BlueZ 1/2] gatt-api: Add error code ReadValue/WriteValue Luiz Augusto von Dentz
2022-08-25 20:07 ` [PATCH BlueZ 2/2] gatt: Parse error message Luiz Augusto von Dentz
2022-08-25 21:09 ` bluez.test.bot [this message]
2022-08-29 19:50 ` [PATCH BlueZ 1/2] gatt-api: Add error code ReadValue/WriteValue 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=6307e4ed.050a0220.cbc81.04b4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox