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:
l2cap-tester.log
Description: Binary data
Attachment:
bnep-tester.log
Description: Binary data
Attachment:
mgmt-tester.log
Description: Binary data
Attachment:
rfcomm-tester.log
Description: Binary data
Attachment:
sco-tester.log
Description: Binary data
Attachment:
smp-tester.log
Description: Binary data
Attachment:
userchan-tester.log
Description: Binary data
