From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zhaochengyi@uniontech.com
Subject: RE: adapter: Add retry when bonding device returns connection failure
Date: Fri, 28 Jun 2024 05:45:35 -0700 (PDT) [thread overview]
Message-ID: <667eb06f.050a0220.6e30f.2e6a@mx.google.com> (raw)
In-Reply-To: <20240628101348.16820-1-zhaochengyi@uniontech.com>
[-- Attachment #1: Type: text/plain, Size: 2696 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=866519
---Test result---
Test Summary:
CheckPatch FAIL 0.63 seconds
GitLint FAIL 0.58 seconds
BuildEll PASS 28.40 seconds
BluezMake PASS 2669.45 seconds
MakeCheck PASS 14.22 seconds
MakeDistcheck PASS 201.46 seconds
CheckValgrind PASS 287.73 seconds
CheckSmatch PASS 390.07 seconds
bluezmakeextell PASS 140.54 seconds
IncrementalBuild PASS 2641.40 seconds
ScanBuild PASS 1202.42 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
adapter: Add retry when bonding device returns connection failure
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#61:
bluetoothd[1539]: src/adapter.c:pair_device_complete() Connect Failed (0x04)
/github/workspace/src/src/13715936.patch total: 0 errors, 1 warnings, 16 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/src/13715936.patch has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
adapter: Add retry when bonding device returns connection failure
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
11: B1 Line exceeds max length (106>80): "bluetoothd[1539]: src/adapter.c:bonding_attempt_complete() hci0 bdaddr DD:EC:0F:57:A9:2E type 2 status 0x4"
12: B1 Line exceeds max length (89>80): "bluetoothd[1539]: src/device.c:device_bonding_complete() bonding 0x5591f87230 status 0x04"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-06-28 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 10:13 [PATCH] adapter: Add retry when bonding device returns connection failure Chengyi Zhao
2024-06-28 12:45 ` bluez.test.bot [this message]
2024-06-28 14:00 ` Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2024-07-01 10:12 Chengyi Zhao
2024-07-01 11:53 ` bluez.test.bot
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=667eb06f.050a0220.6e30f.2e6a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zhaochengyi@uniontech.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