From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, a.fatoum@pengutronix.de
Subject: RE: Bluetooth: hci_sync: complete LE connection on any event
Date: Thu, 16 Jun 2022 03:03:13 -0700 (PDT) [thread overview]
Message-ID: <62aaffe1.1c69fb81.64601.13f7@mx.google.com> (raw)
In-Reply-To: <20220616092418.738877-1-a.fatoum@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2244 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=650944
---Test result---
Test Summary:
CheckPatch FAIL 1.24 seconds
GitLint FAIL 0.68 seconds
SubjectPrefix PASS 0.57 seconds
BuildKernel PASS 30.24 seconds
BuildKernel32 PASS 26.88 seconds
Incremental Build with patchesPASS 37.54 seconds
TestRunner: Setup PASS 461.76 seconds
TestRunner: l2cap-tester PASS 12.67 seconds
TestRunner: bnep-tester PASS 5.63 seconds
TestRunner: mgmt-tester PASS 96.61 seconds
TestRunner: rfcomm-tester PASS 9.16 seconds
TestRunner: sco-tester PASS 8.80 seconds
TestRunner: smp-tester PASS 8.85 seconds
TestRunner: userchan-tester PASS 5.89 seconds
Details
##############################
Test: CheckPatch - FAIL - 1.24 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
Bluetooth: hci_sync: complete LE connection on any event\WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#77:
[1]: https://lore.kernel.org/linux-bluetooth/a1ce1743-e450-6cdb-dfab-56a3e3eb9aed@pengutronix.de/
total: 0 errors, 1 warnings, 0 checks, 18 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/12883653.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL - 0.68 seconds
Run gitlint with rule in .gitlint
Bluetooth: hci_sync: complete LE connection on any event
14: B1 Line exceeds max length (97>80): "[1]: https://lore.kernel.org/linux-bluetooth/a1ce1743-e450-6cdb-dfab-56a3e3eb9aed@pengutronix.de/"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-06-16 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 9:24 [PATCH] Bluetooth: hci_sync: complete LE connection on any event Ahmad Fatoum
2022-06-16 10:03 ` bluez.test.bot [this message]
2022-06-19 11:57 ` Thorsten Leemhuis
2022-06-20 9:58 ` Ahmad Fatoum
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=62aaffe1.1c69fb81.64601.13f7@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=a.fatoum@pengutronix.de \
--cc=linux-bluetooth@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).