RE: [BlueZ,v1,1/3] monitor: Add L2CAP channel details to analyze output

[bluez.test.bot@gmail.com]

[-- Attachment #1: Type: text/plain, Size: 1648 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=1081747

---Test result---

Test Summary:
CheckPatch                    PASS      1.40 seconds
GitLint                       FAIL      1.61 seconds
BuildEll                      PASS      18.08 seconds
BluezMake                     PASS      673.13 seconds
MakeCheck                     PASS      18.27 seconds
MakeDistcheck                 PASS      227.65 seconds
CheckValgrind                 PASS      277.64 seconds
CheckSmatch                   PASS      317.95 seconds
bluezmakeextell               PASS      172.05 seconds
IncrementalBuild              PASS      705.73 seconds
ScanBuild                     PASS      957.94 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v1,2/3] monitor: Use wall-clock duration for throughput and add min/max speed

WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
1: T1 Title exceeds max length (84>80): "[BlueZ,v1,2/3] monitor: Use wall-clock duration for throughput and add min/max speed"


https://github.com/bluez/bluez/pull/2042

---
Regards,
Linux Bluetooth