From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: Add mgmt event for BIGInfo report
Date: Mon, 21 Aug 2023 07:01:21 -0700 (PDT) [thread overview]
Message-ID: <64e36e31.c80a0220.be2f3.424c@mx.google.com> (raw)
In-Reply-To: <20230821120353.28711-2-iulia.tanasescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1716 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=777863
---Test result---
Test Summary:
CheckPatch PASS 2.25 seconds
GitLint PASS 1.48 seconds
BuildEll PASS 27.72 seconds
BluezMake PASS 874.91 seconds
MakeCheck PASS 11.89 seconds
MakeDistcheck PASS 158.93 seconds
CheckValgrind PASS 261.98 seconds
CheckSmatch WARNING 352.57 seconds
bluezmakeextell PASS 105.61 seconds
IncrementalBuild PASS 2928.70 seconds
ScanBuild PASS 1084.68 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:1856: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 structuresmonitor/packet.c: note: in included file:monitor/display.h:82:26: warning: Variable length array is used.monitor/packet.c:1856: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-08-21 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 12:03 [PATCH BlueZ 0/4] Add mgmt event for BIGInfo report Iulia Tanasescu
2023-08-21 12:03 ` [PATCH BlueZ 1/4] lib/mgmt: " Iulia Tanasescu
2023-08-21 14:01 ` bluez.test.bot [this message]
2023-08-21 12:03 ` [PATCH BlueZ 2/4] monitor: Add decoding support for BIGInfo mgmt event Iulia Tanasescu
2023-08-21 12:03 ` [PATCH BlueZ 3/4] monitor: Fix decoding issue for hci BIGInfo report Iulia Tanasescu
2023-08-21 12:03 ` [PATCH BlueZ 4/4] lib: Add sync_handle to bcast QoS Iulia Tanasescu
-- strict thread matches above, loose matches on Subject: below --
2023-08-24 10:24 [PATCH BlueZ 1/4] lib/mgmt: Add mgmt event for BIGInfo report Iulia Tanasescu
2023-08-24 12:49 ` bluez.test.bot
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=64e36e31.c80a0220.be2f3.424c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=iulia.tanasescu@nxp.com \
--cc=linux-bluetooth@vger.kernel.org \
/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).