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=516913 ---Test result--- Test Summary: CheckPatch FAIL 1.11 seconds GitLint FAIL 0.12 seconds BuildKernel PASS 680.73 seconds TestRunner: Setup PASS 445.11 seconds TestRunner: l2cap-tester PASS 3.15 seconds TestRunner: bnep-tester PASS 2.21 seconds TestRunner: mgmt-tester PASS 35.57 seconds TestRunner: rfcomm-tester PASS 2.48 seconds TestRunner: sco-tester PASS 2.44 seconds TestRunner: smp-tester FAIL 2.50 seconds TestRunner: userchan-tester PASS 2.32 seconds Details ############################## Test: CheckPatch - FAIL - 1.11 seconds Run checkpatch.pl script with rule in .checkpatch.conf Bluetooth: hci_sock: Fix calling lock_sock when handling HCI_DEV_UNREG WARNING: Unknown commit id 'e305509e678b3a4a', maybe rebased or not pulled? #18: Fixes: e305509e678b3a4a ("Bluetooth: use correct lock to prevent UAF of hdev object") total: 0 errors, 1 warnings, 0 checks, 389 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_sock: Fix calling lock_sock when handling" 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 - FAIL - 0.12 seconds Run gitlint with rule in .gitlint Bluetooth: hci_sock: Fix calling lock_sock when handling HCI_DEV_UNREG 14: B1 Line exceeds max length (85>80): "Fixes: e305509e678b3a4a ("Bluetooth: use correct lock to prevent UAF of hdev object")" ############################## Test: BuildKernel - PASS - 680.73 seconds Build Kernel with minimal configuration supports Bluetooth ############################## Test: TestRunner: Setup - PASS - 445.11 seconds Setup environment for running Test Runner ############################## Test: TestRunner: l2cap-tester - PASS - 3.15 seconds Run test-runner with l2cap-tester Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: bnep-tester - PASS - 2.21 seconds Run test-runner with bnep-tester Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: mgmt-tester - PASS - 35.57 seconds Run test-runner with mgmt-tester Total: 446, Passed: 443 (99.3%), Failed: 0, Not Run: 3 ############################## Test: TestRunner: rfcomm-tester - PASS - 2.48 seconds Run test-runner with rfcomm-tester Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: sco-tester - PASS - 2.44 seconds Run test-runner with sco-tester Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: smp-tester - FAIL - 2.50 seconds Run test-runner with smp-tester Total: 8, Passed: 7 (87.5%), Failed: 1, Not Run: 0 Failed Test Cases SMP Client - SC Request 2 Failed 0.033 seconds ############################## Test: TestRunner: userchan-tester - PASS - 2.32 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
