From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ] monitor: Fix using PACKET_FILTER_SHOW_SCO_DATA for ISO packets
Date: Wed, 17 May 2023 16:09:17 -0700 (PDT) [thread overview]
Message-ID: <64655e9d.920a0220.309d7.08f6@mx.google.com> (raw)
In-Reply-To: <20230517215852.1395512-1-luiz.dentz@gmail.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=748669
---Test result---
Test Summary:
CheckPatch PASS 0.45 seconds
GitLint PASS 0.30 seconds
BuildEll PASS 26.47 seconds
BluezMake PASS 791.91 seconds
MakeCheck PASS 11.49 seconds
MakeDistcheck PASS 155.08 seconds
CheckValgrind PASS 247.47 seconds
CheckSmatch WARNING 336.29 seconds
bluezmakeextell PASS 101.00 seconds
IncrementalBuild PASS 660.64 seconds
ScanBuild PASS 1013.03 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:1801:26: warning: Variable length array is used.monitor/packet.c: note: in included file:monitor/bt.h:3552:52: warning: array of flexible structuresmonitor/bt.h:3540:40: warning: array of flexible structures
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-05-17 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 21:58 [PATCH BlueZ] monitor: Fix using PACKET_FILTER_SHOW_SCO_DATA for ISO packets Luiz Augusto von Dentz
2023-05-17 23:09 ` bluez.test.bot [this message]
2023-05-18 19: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=64655e9d.920a0220.309d7.08f6@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;
as well as URLs for NNTP newsgroup(s).