From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: Add 6lowpan-tester
Date: Sun, 05 Oct 2025 16:42:16 -0700 (PDT) [thread overview]
Message-ID: <68e30258.6b0a0220.947d0.6ae5@mx.google.com> (raw)
In-Reply-To: <8c38a793c1016bbf49d90b89cf4df2fc8b6419a8.1759702519.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 2014 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=1008564
---Test result---
Test Summary:
CheckPatch PENDING 0.23 seconds
GitLint PENDING 0.34 seconds
BuildEll PASS 20.02 seconds
BluezMake PASS 2682.42 seconds
MakeCheck PASS 20.07 seconds
MakeDistcheck PASS 185.23 seconds
CheckValgrind PASS 237.40 seconds
CheckSmatch WARNING 308.46 seconds
bluezmakeextell PASS 128.98 seconds
IncrementalBuild PENDING 0.29 seconds
ScanBuild PASS 921.00 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:699:28: warning: Variable length array is used.emulator/bthost.c:700:32: warning: Variable length array is used.emulator/bthost.c:917:28: warning: Variable length array is used.emulator/bthost.c:951:28: warning: Variable length array is used.emulator/bthost.c:952:32: warning: Variable length array is used.emulator/bthost.c:699:28: warning: Variable length array is used.emulator/bthost.c:700:32: warning: Variable length array is used.emulator/bthost.c:917:28: warning: Variable length array is used.emulator/bthost.c:951:28: warning: Variable length array is used.emulator/bthost.c:952:32: warning: Variable length array is used.
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-10-05 23:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-05 22:17 [PATCH BlueZ 0/4] Add 6lowpan-tester Pauli Virtanen
2025-10-05 22:17 ` [PATCH BlueZ 1/4] bthost: handle L2CAP_DISCONN_RSP and remove l2cap_conns Pauli Virtanen
2025-10-05 23:42 ` bluez.test.bot [this message]
2025-10-05 22:17 ` [PATCH BlueZ 2/4] bthost: handle L2CAP_FLOW_CONTROL_CREDIT_IND Pauli Virtanen
2025-10-05 22:17 ` [PATCH BlueZ 3/4] tools: add 6lowpan-tester Pauli Virtanen
2025-10-13 17:20 ` Luiz Augusto von Dentz
2025-10-05 22:17 ` [PATCH BlueZ 4/4] doc: enable 6lowpan in tester.config and explain in test-runner.rst Pauli Virtanen
2025-10-13 17:40 ` [PATCH BlueZ 0/4] Add 6lowpan-tester patchwork-bot+bluetooth
2025-10-13 19:00 ` 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=68e30258.6b0a0220.947d0.6ae5@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