From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1,1/8] doc/btmon: Add missing documentation
Date: Thu, 19 Feb 2026 09:57:37 -0800 (PST) [thread overview]
Message-ID: <69974f11.050a0220.f7f51.b1b7@mx.google.com> (raw)
In-Reply-To: <20260219162230.3074355-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1812 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=1055603
---Test result---
Test Summary:
CheckPatch PENDING 0.44 seconds
GitLint PENDING 0.48 seconds
BuildEll PASS 21.54 seconds
BluezMake PASS 642.32 seconds
MakeCheck PASS 18.62 seconds
MakeDistcheck PASS 252.23 seconds
CheckValgrind PASS 298.02 seconds
CheckSmatch WARNING 361.63 seconds
bluezmakeextell PASS 184.14 seconds
IncrementalBuild PENDING 0.32 seconds
ScanBuild PASS 1063.68 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/packet.c:1993: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 structuresmonitor/packet.c:1993: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
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-02-19 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 16:22 [PATCH BlueZ v1 1/8] doc/btmon: Add missing documentation Luiz Augusto von Dentz
2026-02-19 16:22 ` [PATCH BlueZ v1 2/8] doc/btmon: Add dedicate sections for timestamp and frame number Luiz Augusto von Dentz
2026-02-19 16:22 ` [PATCH BlueZ v1 3/8] doc/btmon: Add connection tracking section Luiz Augusto von Dentz
2026-02-19 16:22 ` [PATCH BlueZ v1 4/8] doc/btmon: Add a dedicated section for analyze mode Luiz Augusto von Dentz
2026-02-19 16:22 ` [PATCH BlueZ v1 5/8] doc/btmon: Add a section for automated trace analysis Luiz Augusto von Dentz
2026-02-19 16:22 ` [PATCH BlueZ v1 6/8] monitor: Annotate ACL/SCO/ISO data with device address Luiz Augusto von Dentz
2026-02-19 16:22 ` [PATCH BlueZ v1 7/8] monitor: Print connection type in Disconnect Complete Luiz Augusto von Dentz
2026-02-19 16:22 ` [PATCH BlueZ v1 8/8] monitor: Add connection lifecycle to analyze summary Luiz Augusto von Dentz
2026-02-19 17:57 ` 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=69974f11.050a0220.f7f51.b1b7@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