From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ceggers@arri.de
Subject: RE: mesh: cleanups and a bugfix for relay packets
Date: Fri, 11 Jul 2025 16:26:54 -0700 (PDT) [thread overview]
Message-ID: <68719dbe.170a0220.3a4a61.76dc@mx.google.com> (raw)
In-Reply-To: <20250711220035.10065-2-ceggers@arri.de>
[-- Attachment #1: Type: text/plain, Size: 1497 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=981661
---Test result---
Test Summary:
CheckPatch PENDING 0.36 seconds
GitLint PENDING 0.35 seconds
BuildEll PASS 20.11 seconds
BluezMake PASS 2544.29 seconds
MakeCheck PASS 20.37 seconds
MakeDistcheck PASS 185.20 seconds
CheckValgrind PASS 234.67 seconds
CheckSmatch WARNING 305.40 seconds
bluezmakeextell PASS 127.19 seconds
IncrementalBuild PENDING 0.36 seconds
ScanBuild PASS 908.82 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:
mesh/mesh-io-mgmt.c:525:67: warning: Variable length array is used.mesh/mesh-io-mgmt.c:525:67: 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-07-11 23:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 21:57 [PATCH Bluez v2 0/9] mesh: cleanups and a bugfix for relay packets Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 1/9] mesh: net-keys: more uses of BEACON_LEN_SNB and BEACON_LEN_MPB Christian Eggers
2025-07-11 23:26 ` bluez.test.bot [this message]
2025-07-11 21:57 ` [PATCH BlueZ v2 2/9] mesh: introduce MESH_AD_MAX_LEN and MESH_NET_MAX_PDU_LEN Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 3/9] mesh: replace MESH internal defines by shared ones Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 4/9] mesh: net: constify tx path Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 5/9] mesh: net: remove unused stuff Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 6/9] mesh: net: update comment Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 7/9] mesh: crypto: mesh_crypto_aes_ccm_encrypt(): remove unused parameter Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 8/9] mesh: crypto: simplify mesh_crypto_packet_parse() Christian Eggers
2025-07-11 21:57 ` [PATCH BlueZ v2 9/9] mesh: fix corrupted relay packets Christian Eggers
2025-07-15 14:30 ` [PATCH Bluez v2 0/9] mesh: cleanups and a bugfix for " patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2025-07-11 17:39 [PATCH BlueZ 1/9] mesh: net-keys: more uses of BEACON_LEN_SNB and BEACON_LEN_MPB Christian Eggers
2025-07-11 18:50 ` mesh: cleanups and a bugfix for relay packets bluez.test.bot
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=68719dbe.170a0220.3a4a61.76dc@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=ceggers@arri.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox