From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1] test-mesh-crypto: Don't attempt to run test if AF_ALG is not available
Date: Fri, 22 May 2026 11:46:02 -0700 (PDT) [thread overview]
Message-ID: <6a10a46a.27addf4e.278d9.ef92@mx.google.com> (raw)
In-Reply-To: <20260522164912.3253018-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1283 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=1099512
---Test result---
Test Summary:
CheckPatch PASS 0.48 seconds
GitLint FAIL 0.34 seconds
BuildEll PASS 21.21 seconds
BluezMake PASS 672.94 seconds
MakeCheck PASS 19.04 seconds
MakeDistcheck PASS 248.00 seconds
CheckValgrind PASS 294.89 seconds
CheckSmatch PASS 350.97 seconds
bluezmakeextell PASS 183.30 seconds
IncrementalBuild PASS 675.76 seconds
ScanBuild PASS 1070.01 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v1] test-mesh-crypto: Don't attempt to run test if AF_ALG is not available
1: T1 Title exceeds max length (81>80): "[BlueZ,v1] test-mesh-crypto: Don't attempt to run test if AF_ALG is not available"
https://github.com/bluez/bluez/pull/2147
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-05-22 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 16:49 [PATCH BlueZ v1] test-mesh-crypto: Don't attempt to run test if AF_ALG is not available Luiz Augusto von Dentz
2026-05-22 18:46 ` bluez.test.bot [this message]
2026-05-26 15:40 ` 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=6a10a46a.27addf4e.278d9.ef92@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