From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ceggers@arri.de
Subject: RE: [BlueZ,01/15] mesh: crypto: remove dead function declaration
Date: Tue, 08 Jul 2025 07:21:23 -0700 (PDT) [thread overview]
Message-ID: <686d2963.170a0220.1a83c4.1b2b@mx.google.com> (raw)
In-Reply-To: <20250708125947.11988-1-ceggers@arri.de>
[-- Attachment #1: Type: text/plain, Size: 1430 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=980052
---Test result---
Test Summary:
CheckPatch PENDING 0.46 seconds
GitLint PENDING 0.37 seconds
BuildEll PASS 20.75 seconds
BluezMake PASS 2714.98 seconds
MakeCheck PASS 20.33 seconds
MakeDistcheck PASS 186.42 seconds
CheckValgrind PASS 236.01 seconds
CheckSmatch WARNING 307.45 seconds
bluezmakeextell PASS 128.36 seconds
IncrementalBuild PENDING 0.45 seconds
ScanBuild PASS 922.86 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.
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-07-08 14:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 12:59 [PATCH BlueZ 01/15] mesh: crypto: remove dead function declaration Christian Eggers
2025-07-08 12:59 ` [PATCH BlueZ 02/15] mesh: crypto: remove unused function parameter Christian Eggers
2025-07-08 12:59 ` [PATCH BlueZ 03/15] mesh: friend: remove dead function declarations Christian Eggers
2025-07-08 12:59 ` [PATCH BlueZ 04/15] mesh: mesh-config: remove dead function prototype Christian Eggers
2025-07-08 12:59 ` [PATCH BlueZ 05/15] mesh: mesh-io-mgmt: Fix NULL pointer dereference Christian Eggers
2025-07-08 12:59 ` [PATCH BlueZ 06/15] mesh: model: remove dead function prototype Christian Eggers
2025-07-08 12:59 ` [PATCH BlueZ 07/15] mesh: net: remove unused stuff Christian Eggers
2025-07-08 12:59 ` [PATCH BlueZ 08/15] mesh: net: update comment Christian Eggers
2025-07-08 12:59 ` [PATCH BlueZ 09/15] mesh: net: remove obsolete struct net_key Christian Eggers
2025-07-08 12:59 ` [PATCH BlueZ 10/15] mesh: net-keys: introduce BEACON_LEN_SNB, BEACON_LEN_MPB, BEACON_LEN_MAX Christian Eggers
2025-07-08 12:59 ` [PATCH BlueZ 11/15] mesh: net-keys: remove dead function prototype Christian Eggers
2025-07-08 12:59 ` [PATCH BlueZ 12/15] mesh: node: " Christian Eggers
2025-07-08 12:59 ` [PATCH BlueZ 13/15] mesh: prov: cleanup header Christian Eggers
2025-07-08 12:59 ` [PATCH BlueZ 14/15] mesh: remove unneeded casts to bool Christian Eggers
2025-07-08 12:59 ` [PATCH BlueZ 15/15] mesh: use '0x1' rathen than 'true' for bit operations Christian Eggers
2025-07-08 14:21 ` bluez.test.bot [this message]
2025-07-08 14:59 ` [PATCH BlueZ 01/15] mesh: crypto: remove dead function declaration Luiz Augusto von Dentz
2025-07-08 15:07 ` Christian Eggers
2025-07-08 19:30 ` patchwork-bot+bluetooth
2025-07-08 19:45 ` Luiz Augusto von Dentz
2025-07-15 14:30 ` 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=686d2963.170a0220.1a83c4.1b2b@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