From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1] gatt-database: Fix sending notification to all devices
Date: Thu, 18 Apr 2024 14:43:04 -0700 (PDT) [thread overview]
Message-ID: <662193e8.170a0220.494b8.7f76@mx.google.com> (raw)
In-Reply-To: <20240418194723.1440686-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1296 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=845939
---Test result---
Test Summary:
CheckPatch PASS 0.26 seconds
GitLint PASS 0.18 seconds
BuildEll PASS 24.77 seconds
BluezMake PASS 1733.68 seconds
MakeCheck PASS 13.70 seconds
MakeDistcheck PASS 178.89 seconds
CheckValgrind PASS 248.20 seconds
CheckSmatch PASS 355.07 seconds
bluezmakeextell PASS 120.05 seconds
IncrementalBuild PASS 1575.95 seconds
ScanBuild WARNING 1022.75 seconds
Details
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
src/gatt-database.c:1155: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:[~2024-04-18 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 19:47 [PATCH BlueZ v1] gatt-database: Fix sending notification to all devices Luiz Augusto von Dentz
2024-04-18 21:43 ` bluez.test.bot [this message]
2024-04-22 15:40 ` 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=662193e8.170a0220.494b8.7f76@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