From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [BlueZ,v3] tools/l2cap-tester: test closing sockets with ECRED defer
Date: Tue, 01 Sep 2026 16:07:54 -0700 (PDT) [thread overview]
Message-ID: <6a975aca.5003ab28.3a895e.e78f@mx.google.com> (raw)
In-Reply-To: <eb21dbe69ad000c457f63d0de3caf2aa68dbebd8.1788296637.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 1203 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=1155668
---Test result---
Test Summary:
CheckPatch PASS 0.35 seconds
GitLint FAIL 0.22 seconds
BuildEll PASS 15.86 seconds
BluezMake PASS 507.90 seconds
CheckSmatch PASS 229.69 seconds
bluezmakeextell PASS 73.75 seconds
IncrementalBuild PASS 434.74 seconds
ScanBuild PASS 680.79 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v3] tools/l2cap-tester: test closing sockets with ECRED defer
13: B1 Line exceeds max length (92>80): " commit 62df5992 ("Bluetooth: L2CAP: hold conn->lock for __l2cap_ecred_conn_rsp_defer")"
14: B2 Line has trailing whitespace: " "
17: B2 Line has trailing whitespace: " "
https://github.com/bluez/bluez/pull/2468
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-09-01 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 21:05 [PATCH BlueZ v3] tools/l2cap-tester: test closing sockets with ECRED defer Pauli Virtanen
2026-09-01 23:07 ` 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=6a975aca.5003ab28.3a895e.e78f@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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.