From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1,1/4] gatt-server: Check prepare write length before reallocating
Date: Thu, 10 Sep 2026 13:06:00 -0700 (PDT) [thread overview]
Message-ID: <6aa30da8.bdc42a90.83d5c.978b@mx.google.com> (raw)
In-Reply-To: <20260910184216.1601639-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1263 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/series/1162311/
---Test result---
Test Summary:
CheckPatch PASS 1.18 seconds
GitLint FAIL 0.78 seconds
BuildEll PASS 19.61 seconds
BluezMake PASS 382.03 seconds
MakeCheck PASS 14.41 seconds
MakeDistcheck PASS 138.47 seconds
CheckValgrind PASS 233.42 seconds
CheckSmatch PASS 288.75 seconds
bluezmakeextell PASS 92.09 seconds
IncrementalBuild PASS 423.28 seconds
ScanBuild PASS 1123.91 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v1,4/4] client/bluetoothctl: Declare the controller helper in its own header
1: T1 Title exceeds max length (83>80): "[BlueZ,v1,4/4] client/bluetoothctl: Declare the controller helper in its own header"
https://github.com/bluez/bluez/pull/2518
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-09-10 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 18:42 [PATCH BlueZ v1 1/4] gatt-server: Check prepare write length before reallocating Luiz Augusto von Dentz
2026-09-10 18:42 ` [PATCH BlueZ v1 2/4] adapter: Unify the A2DP admin allowlist UUID mapping Luiz Augusto von Dentz
2026-09-10 18:42 ` [PATCH BlueZ v1 3/4] battery: Document the unknown sentinels and fix a stale name Luiz Augusto von Dentz
2026-09-10 18:42 ` [PATCH BlueZ v1 4/4] client/bluetoothctl: Declare the controller helper in its own header Luiz Augusto von Dentz
2026-09-10 20:06 ` bluez.test.bot [this message]
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=6aa30da8.bdc42a90.83d5c.978b@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.