From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, marex@denx.de
Subject: RE: [BlueZ] tools: Make hciattach_* firmware path build-time configurable
Date: Tue, 01 Nov 2022 06:37:43 -0700 (PDT) [thread overview]
Message-ID: <63612127.4a0a0220.ee3ae.be5c@mx.google.com> (raw)
In-Reply-To: <20221101115333.18223-1-marex@denx.de>
[-- Attachment #1: Type: text/plain, Size: 2032 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=690839
---Test result---
Test Summary:
CheckPatch PASS 1.01 seconds
GitLint PASS 0.86 seconds
Prep - Setup ELL PASS 26.44 seconds
Build - Prep PASS 0.68 seconds
Build - Configure PASS 8.16 seconds
Build - Make PASS 723.76 seconds
Make Check PASS 10.90 seconds
Make Check w/Valgrind PASS 287.82 seconds
Make Distcheck PASS 233.70 seconds
Build w/ext ELL - Configure PASS 8.17 seconds
Build w/ext ELL - Make PASS 83.94 seconds
Incremental Build w/ patches PASS 0.00 seconds
Scan Build WARNING 476.19 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.
*****************************************************************************
tools/hciattach_qualcomm.c:218:8: warning: Although the value stored to 'n' is used in the enclosing expression, the value is never actually read from 'n'
if ((n = read_hci_event(fd, resp, 100)) < 0) {
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tools/hciattach_qualcomm.c:253:8: warning: Although the value stored to 'n' is used in the enclosing expression, the value is never actually read from 'n'
if ((n = read_hci_event(fd, resp, 100)) < 0) {
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2 warnings generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-11-01 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 11:53 [PATCH BlueZ] tools: Make hciattach_* firmware path build-time configurable Marek Vasut
2022-11-01 13:37 ` bluez.test.bot [this message]
2022-11-01 15:19 ` [BlueZ] " Marek Vasut
2022-11-01 19:24 ` Luiz Augusto von Dentz
2022-11-01 20:27 ` Marek Vasut
2022-11-01 21:10 ` [PATCH BlueZ] " 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=63612127.4a0a0220.ee3ae.be5c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marex@denx.de \
/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.