From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [BlueZ,1/5] monitor: check data size properly in evt_num_completed_packets
Date: Mon, 06 Apr 2026 05:44:36 -0700 (PDT) [thread overview]
Message-ID: <69d3aab4.050a0220.81617.eb10@mx.google.com> (raw)
In-Reply-To: <adc251f251ef88ee958f6f79cb3cbfe27bda721c.1775474498.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 2059 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=1077640
---Test result---
Test Summary:
CheckPatch PENDING 0.26 seconds
GitLint PENDING 0.26 seconds
BuildEll PASS 20.61 seconds
BluezMake PASS 631.40 seconds
MakeCheck PASS 18.41 seconds
MakeDistcheck PASS 246.49 seconds
CheckValgrind PASS 293.33 seconds
CheckSmatch WARNING 350.53 seconds
bluezmakeextell PASS 184.29 seconds
IncrementalBuild PENDING 0.27 seconds
ScanBuild PASS 1010.97 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:
emulator/bthost.c:703:28: warning: Variable length array is used.emulator/bthost.c:704:32: warning: Variable length array is used.emulator/bthost.c:944:28: warning: Variable length array is used.emulator/bthost.c:978:28: warning: Variable length array is used.emulator/bthost.c:979:32: warning: Variable length array is used.src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):tools/seq2bseq.c:57:26: warning: Variable length array is used.
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
https://github.com/bluez/bluez/pull/2018/checks
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-04-06 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 11:23 [PATCH BlueZ 1/5] monitor: check data size properly in evt_num_completed_packets Pauli Virtanen
2026-04-06 11:23 ` [PATCH BlueZ 2/5] emulator: Remove assigned but unused variables Pauli Virtanen
2026-04-06 11:23 ` [PATCH BlueZ 3/5] monitor: " Pauli Virtanen
2026-04-06 11:23 ` [PATCH BlueZ 4/5] src: " Pauli Virtanen
2026-04-06 11:23 ` [PATCH BlueZ 5/5] tools: " Pauli Virtanen
2026-04-06 12:44 ` bluez.test.bot [this message]
2026-04-06 17:00 ` [PATCH BlueZ 1/5] monitor: check data size properly in evt_num_completed_packets 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=69d3aab4.050a0220.81617.eb10@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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