From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [1/2] Bluetooth: Add helper for serialized HCI command execution
Date: Thu, 20 May 2021 10:49:52 -0700 (PDT) [thread overview]
Message-ID: <60a6a140.1c69fb81.6ec8c.21e6@mx.google.com> (raw)
In-Reply-To: <20210520164213.1381518-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4006 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=485957
---Test result---
Test Summary:
CheckPatch FAIL 2.33 seconds
GitLint PASS 0.21 seconds
BuildKernel PASS 554.04 seconds
TestRunner: Setup PASS 377.70 seconds
TestRunner: l2cap-tester PASS 2.85 seconds
TestRunner: bnep-tester PASS 2.02 seconds
TestRunner: mgmt-tester PASS 28.06 seconds
TestRunner: rfcomm-tester PASS 2.16 seconds
TestRunner: sco-tester PASS 2.08 seconds
TestRunner: smp-tester PASS 2.27 seconds
TestRunner: userchan-tester PASS 1.98 seconds
Details
##############################
Test: CheckPatch - FAIL - 2.33 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
Bluetooth: hci_sync: Make use of hci_cmd_sync_queue
CHECK: Prefer kernel type 'u8' over 'uint8_t'
#53: FILE: net/bluetooth/hci_request.c:196:
+ uint8_t status;
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#71:
new file mode 100644
CHECK: braces {} should be used on all arms of this statement
#208: FILE: net/bluetooth/hci_sync.c:133:
+ if (name_len > 48) {
[...]
+ } else
[...]
CHECK: Unbalanced braces around else statement
#211: FILE: net/bluetooth/hci_sync.c:136:
+ } else
CHECK: No space is necessary after a cast
#225: FILE: net/bluetooth/hci_sync.c:150:
+ ptr[2] = (u8) hdev->inq_tx_power;
CHECK: Prefer kernel type 'u8' over 'uint8_t'
#384: FILE: net/bluetooth/mgmt.c:2095:
+ uint8_t status;
CHECK: Prefer kernel type 'u8' over 'uint8_t'
#434: FILE: net/bluetooth/mgmt.c:2171:
+ uint8_t status;
CHECK: Prefer kernel type 'u8' over 'uint8_t'
#484: FILE: net/bluetooth/mgmt.c:2254:
+ uint8_t status = 0;
total: 0 errors, 1 warnings, 7 checks, 509 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: hci_sync: Make use of hci_cmd_sync_queue" 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.21 seconds
Run gitlint with rule in .gitlint
##############################
Test: BuildKernel - PASS - 554.04 seconds
Build Kernel with minimal configuration supports Bluetooth
##############################
Test: TestRunner: Setup - PASS - 377.70 seconds
Setup environment for running Test Runner
##############################
Test: TestRunner: l2cap-tester - PASS - 2.85 seconds
Run test-runner with l2cap-tester
Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: bnep-tester - PASS - 2.02 seconds
Run test-runner with bnep-tester
Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: mgmt-tester - PASS - 28.06 seconds
Run test-runner with mgmt-tester
Total: 416, Passed: 403 (96.9%), Failed: 0, Not Run: 13
##############################
Test: TestRunner: rfcomm-tester - PASS - 2.16 seconds
Run test-runner with rfcomm-tester
Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: sco-tester - PASS - 2.08 seconds
Run test-runner with sco-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: smp-tester - PASS - 2.27 seconds
Run test-runner with smp-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: userchan-tester - PASS - 1.98 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: 44350 bytes --]
[-- Attachment #3: bnep-tester.log --]
[-- Type: application/octet-stream, Size: 3557 bytes --]
[-- Attachment #4: mgmt-tester.log --]
[-- Type: application/octet-stream, Size: 546637 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 --]
prev parent reply other threads:[~2021-05-20 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 16:42 [PATCH 1/2] Bluetooth: Add helper for serialized HCI command execution Luiz Augusto von Dentz
2021-05-20 16:42 ` [PATCH 2/2] Bluetooth: hci_sync: Make use of hci_cmd_sync_queue Luiz Augusto von Dentz
2021-05-20 20:17 ` Marcel Holtmann
2021-05-20 23:57 ` Luiz Augusto von Dentz
2021-05-20 17:49 ` 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=60a6a140.1c69fb81.6ec8c.21e6@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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;
as well as URLs for NNTP newsgroup(s).