From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, me@prestonhunt.com
Subject: RE: btmon/TDS: decode org 0x02 as Wi-Fi Alliance
Date: Fri, 08 May 2026 19:14:35 -0700 (PDT) [thread overview]
Message-ID: <69fe988b.050a0220.2f853.3ca7@mx.google.com> (raw)
In-Reply-To: <20260509002249.2771777-2-me@prestonhunt.com>
[-- Attachment #1: Type: text/plain, Size: 1323 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=1091848
---Test result---
Test Summary:
CheckPatch PASS 0.34 seconds
GitLint PASS 0.26 seconds
BuildEll PASS 20.23 seconds
BluezMake PASS 643.92 seconds
MakeCheck PASS 0.89 seconds
MakeDistcheck PASS 246.11 seconds
CheckValgrind PASS 218.86 seconds
CheckSmatch WARNING 346.88 seconds
bluezmakeextell PASS 181.91 seconds
IncrementalBuild PASS 639.76 seconds
ScanBuild PASS 1013.45 seconds
Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/packet.c:2000:26: warning: Variable length array is used.monitor/packet.c: note: in included file:monitor/bt.h:3909:52: warning: array of flexible structuresmonitor/bt.h:3897:40: warning: array of flexible structures
https://github.com/bluez/bluez/pull/2113
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-05-09 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 0:22 [PATCH BlueZ 0/1] btmon/TDS: decode org 0x02 as Wi-Fi Alliance Preston Hunt
2026-05-09 0:22 ` [PATCH BlueZ 1/1] btmon: decode " Preston Hunt
2026-05-09 2:14 ` bluez.test.bot [this message]
2026-05-09 9:08 ` [PATCH BlueZ 0/1] btmon/TDS: decode org " Paul Menzel
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=69fe988b.050a0220.2f853.3ca7@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=me@prestonhunt.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