From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/2] device: Fix not always storing device info
Date: Tue, 07 Mar 2023 18:19:05 -0800 (PST) [thread overview]
Message-ID: <6407f099.170a0220.47f45.2cc0@mx.google.com> (raw)
In-Reply-To: <20230308005158.2661414-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1293 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=727684
---Test result---
Test Summary:
CheckPatch PASS 0.71 seconds
GitLint PASS 0.49 seconds
BuildEll PASS 26.25 seconds
BluezMake PASS 763.65 seconds
MakeCheck PASS 11.06 seconds
MakeDistcheck PASS 154.66 seconds
CheckValgrind PASS 241.74 seconds
CheckSmatch PASS 323.62 seconds
bluezmakeextell PASS 97.21 seconds
IncrementalBuild PASS 1235.69 seconds
ScanBuild WARNING 983.36 seconds
Details
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
src/gatt-database.c:1152:10: warning: Value stored to 'bits' during its initialization is never read
uint8_t bits[] = { BT_GATT_CHRC_CLI_FEAT_ROBUST_CACHING,
^~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-03-08 2:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 0:51 [PATCH BlueZ 1/2] device: Fix not always storing device info Luiz Augusto von Dentz
2023-03-08 0:51 ` [PATCH BlueZ 2/2] gatt: Fix creating duplicated objects Luiz Augusto von Dentz
2023-03-08 2:19 ` bluez.test.bot [this message]
2023-03-11 0:40 ` [PATCH BlueZ 1/2] device: Fix not always storing device info 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=6407f099.170a0220.47f45.2cc0@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.