From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, vlad.pruteanu@nxp.com
Subject: RE: monitor: Use proper name for CIS bit
Date: Tue, 12 Sep 2023 01:13:54 -0700 (PDT) [thread overview]
Message-ID: <65001dc2.050a0220.35349.65ef@mx.google.com> (raw)
In-Reply-To: <20230912070319.1224301-2-vlad.pruteanu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1386 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=783284
---Test result---
Test Summary:
CheckPatch PASS 0.54 seconds
GitLint PASS 0.36 seconds
BuildEll PASS 28.66 seconds
BluezMake PASS 902.83 seconds
MakeCheck PASS 12.10 seconds
MakeDistcheck PASS 161.34 seconds
CheckValgrind PASS 261.35 seconds
CheckSmatch WARNING 350.02 seconds
bluezmakeextell PASS 106.12 seconds
IncrementalBuild PASS 729.87 seconds
ScanBuild PASS 1088.43 seconds
Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/packet.c: note: in included file:monitor/display.h:82:26: warning: Variable length array is used.monitor/packet.c:1859:26: warning: Variable length array is used.monitor/packet.c: note: in included file:monitor/bt.h:3606:52: warning: array of flexible structuresmonitor/bt.h:3594:40: warning: array of flexible structures
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-09-12 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 7:03 [PATCH BlueZ 0/1] monitor: Use proper name for CIS bit Vlad Pruteanu
2023-09-12 7:03 ` [PATCH BlueZ 1/1] " Vlad Pruteanu
2023-09-12 8:13 ` bluez.test.bot [this message]
2023-09-12 18:50 ` [PATCH BlueZ 0/1] " 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=65001dc2.050a0220.35349.65ef@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vlad.pruteanu@nxp.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;
as well as URLs for NNTP newsgroup(s).