From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kevin@simpleble.org
Subject: RE: emulator: Fix extended advertising report types
Date: Mon, 05 Oct 2026 13:12:25 -0700 (PDT) [thread overview]
Message-ID: <6ac404a9.b97a138d.16226e.bdaf@mx.google.com> (raw)
In-Reply-To: <20261005162117.4606-2-kevin@simpleble.org>
[-- Attachment #1: Type: text/plain, Size: 1160 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/series/1179769/
---Test result---
Test Summary:
CheckPatch PASS 0.94 seconds
GitLint PASS 1.09 seconds
BuildEll PASS 19.55 seconds
BluezMake PASS 384.09 seconds
CheckSmatch WARNING 292.94 seconds
bluezmakeextell PASS 93.64 seconds
TestFunctional PASS 1127.10 seconds
IncrementalBuild PASS 390.07 seconds
ScanBuild PASS 1108.07 seconds
Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
emulator/btdev.c:479:29: warning: Variable length array is used.emulator/btdev.c:479:29: warning: Variable length array is used.emulator/btdev.c:479:29: warning: Variable length array is used.
https://github.com/bluez/bluez/pull/2628
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-05 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 16:21 [PATCH BlueZ 0/3] emulator: Fix extended advertising report types Kevin Dewald
2026-10-05 16:21 ` [PATCH BlueZ 1/3] emulator: Remove unused le_ext_adv_type Kevin Dewald
2026-10-05 20:12 ` bluez.test.bot [this message]
2026-10-05 16:21 ` [PATCH BlueZ 2/3] emulator: Fix extended scan response Event_Type Kevin Dewald
2026-10-05 16:21 ` [PATCH BlueZ 3/3] emulator: Fix report type after a scan response Kevin Dewald
2026-10-07 18:40 ` [PATCH BlueZ 0/3] emulator: Fix extended advertising report types 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=6ac404a9.b97a138d.16226e.bdaf@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=kevin@simpleble.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.