From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, dlenski@gmail.com
Subject: RE: Bluetooth: Add a new QCA_ROME device (0cf3:e500)
Date: Tue, 18 May 2021 11:37:50 -0700 (PDT) [thread overview]
Message-ID: <60a4097e.1c69fb81.6e189.080d@mx.google.com> (raw)
In-Reply-To: <20210518172546.304882-1-dlenski@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3278 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=484479
---Test result---
Test Summary:
CheckPatch FAIL 0.49 seconds
GitLint PASS 0.11 seconds
BuildKernel PASS 562.85 seconds
TestRunner: Setup PASS 366.25 seconds
TestRunner: l2cap-tester PASS 2.74 seconds
TestRunner: bnep-tester PASS 1.99 seconds
TestRunner: mgmt-tester PASS 27.50 seconds
TestRunner: rfcomm-tester PASS 2.17 seconds
TestRunner: sco-tester PASS 2.15 seconds
TestRunner: smp-tester PASS 2.25 seconds
TestRunner: userchan-tester PASS 1.97 seconds
Details
##############################
Test: CheckPatch - FAIL - 0.49 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
Bluetooth: Add a new QCA_ROME device (0cf3:e500)
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit fatal: bad o ("a0e33f46d8660e1fd")'
#9:
0a03f98b98c201191e3ba15a0e33f46d8660e1fd
total: 1 errors, 0 warnings, 8 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.
"[PATCH] Bluetooth: Add a new QCA_ROME device (0cf3:e500)" has style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - PASS - 0.11 seconds
Run gitlint with rule in .gitlint
##############################
Test: BuildKernel - PASS - 562.85 seconds
Build Kernel with minimal configuration supports Bluetooth
##############################
Test: TestRunner: Setup - PASS - 366.25 seconds
Setup environment for running Test Runner
##############################
Test: TestRunner: l2cap-tester - PASS - 2.74 seconds
Run test-runner with l2cap-tester
Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: bnep-tester - PASS - 1.99 seconds
Run test-runner with bnep-tester
Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: mgmt-tester - PASS - 27.50 seconds
Run test-runner with mgmt-tester
Total: 416, Passed: 403 (96.9%), Failed: 0, Not Run: 13
##############################
Test: TestRunner: rfcomm-tester - PASS - 2.17 seconds
Run test-runner with rfcomm-tester
Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: sco-tester - PASS - 2.15 seconds
Run test-runner with sco-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: smp-tester - PASS - 2.25 seconds
Run test-runner with smp-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: userchan-tester - PASS - 1.97 seconds
Run test-runner with userchan-tester
Total: 3, Passed: 3 (100.0%), Failed: 0, Not Run: 0
---
Regards,
Linux Bluetooth
[-- Attachment #2: l2cap-tester.log --]
[-- Type: application/octet-stream, Size: 44230 bytes --]
[-- Attachment #3: bnep-tester.log --]
[-- Type: application/octet-stream, Size: 3557 bytes --]
[-- Attachment #4: mgmt-tester.log --]
[-- Type: application/octet-stream, Size: 546745 bytes --]
[-- Attachment #5: rfcomm-tester.log --]
[-- Type: application/octet-stream, Size: 11677 bytes --]
[-- Attachment #6: sco-tester.log --]
[-- Type: application/octet-stream, Size: 9912 bytes --]
[-- Attachment #7: smp-tester.log --]
[-- Type: application/octet-stream, Size: 11821 bytes --]
[-- Attachment #8: userchan-tester.log --]
[-- Type: application/octet-stream, Size: 5454 bytes --]
next prev parent reply other threads:[~2021-05-18 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 17:25 [PATCH] Bluetooth: Add a new QCA_ROME device (0cf3:e500) Daniel Lenski
2021-05-18 18:37 ` bluez.test.bot [this message]
2021-05-20 15:12 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2021-05-18 18:59 Daniel Lenski
2021-05-18 19:31 ` bluez.test.bot
2021-05-18 21:41 ` Daniel Lenski
2021-05-18 21:58 ` Tedd Ho-Jeong An
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=60a4097e.1c69fb81.6e189.080d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=dlenski@gmail.com \
--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).