From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, apusaka@google.com
Subject: RE: [BlueZ] monitor: Add decoding for Microsoft defined event
Date: Wed, 15 Apr 2026 02:00:55 -0700 (PDT) [thread overview]
Message-ID: <69df53c7.050a0220.219a9f.7c69@mx.google.com> (raw)
In-Reply-To: <20260415073940.739683-1-apusaka@google.com>
[-- Attachment #1: Type: text/plain, Size: 1421 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=1081435
---Test result---
Test Summary:
CheckPatch PASS 0.48 seconds
GitLint PASS 0.29 seconds
BuildEll PASS 20.08 seconds
BluezMake PASS 641.53 seconds
MakeCheck PASS 18.87 seconds
MakeDistcheck PASS 241.59 seconds
CheckValgrind PASS 287.58 seconds
CheckSmatch WARNING 343.47 seconds
bluezmakeextell PASS 179.33 seconds
IncrementalBuild PASS 659.52 seconds
ScanBuild PASS 999.51 seconds
Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/msft.c: note: in included file:monitor/msft.h:88:44: warning: array of flexible structuresmonitor/packet.c:2002:26: warning: Variable length array is used.monitor/packet.c: note: in included file:monitor/bt.h:3866:52: warning: array of flexible structuresmonitor/bt.h:3854:40: warning: array of flexible structures
https://github.com/bluez/bluez/pull/2038
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-04-15 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 7:36 [PATCH BlueZ] monitor: Add decoding for Microsoft defined event Archie Pusaka
2026-04-15 9:00 ` bluez.test.bot [this message]
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=69df53c7.050a0220.219a9f.7c69@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=apusaka@google.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