From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v2,1/6] shared/crypto: Add bt_crypto_rsi
Date: Thu, 15 Jan 2026 13:48:52 -0800 (PST) [thread overview]
Message-ID: <696960c4.050a0220.c88bb.6d9d@mx.google.com> (raw)
In-Reply-To: <20260115205408.1554101-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1766 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=1043005
---Test result---
Test Summary:
CheckPatch PENDING 0.47 seconds
GitLint PENDING 0.49 seconds
BuildEll PASS 20.06 seconds
BluezMake PASS 635.18 seconds
MakeCheck PASS 18.44 seconds
MakeDistcheck PASS 242.58 seconds
CheckValgrind PASS 297.31 seconds
CheckSmatch WARNING 353.44 seconds
bluezmakeextell PASS 183.34 seconds
IncrementalBuild PENDING 0.34 seconds
ScanBuild PASS 1041.03 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:
src/shared/crypto.c:271:21: warning: Variable length array is used.src/shared/crypto.c:272:23: warning: Variable length array is used.src/shared/crypto.c:271:21: warning: Variable length array is used.src/shared/crypto.c:272:23: warning: Variable length array is used.src/shared/crypto.c:271:21: warning: Variable length array is used.src/shared/crypto.c:272:23: 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:[~2026-01-15 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 20:54 [PATCH BlueZ v2 1/6] shared/crypto: Add bt_crypto_rsi Luiz Augusto von Dentz
2026-01-15 20:54 ` [PATCH BlueZ v2 2/6] advertising: Use bt_crypto_rsi to generate RSI Luiz Augusto von Dentz
2026-01-15 20:54 ` [PATCH BlueZ v2 3/6] advtest: " Luiz Augusto von Dentz
2026-01-15 20:54 ` [PATCH BlueZ v2 4/6] shared/ad: Make bt_ad_has_data return the data Luiz Augusto von Dentz
2026-01-15 20:54 ` [PATCH BlueZ v2 5/6] advertising: Fix not verifying if RSI set is valid Luiz Augusto von Dentz
2026-01-15 20:54 ` [PATCH BlueZ v2 6/6] advtest: Fix displaying RSI as a byte array rather then an address Luiz Augusto von Dentz
2026-01-15 21:48 ` bluez.test.bot [this message]
2026-01-15 22:40 ` [PATCH BlueZ v2 1/6] shared/crypto: Add bt_crypto_rsi 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=696960c4.050a0220.c88bb.6d9d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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