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=500043 ---Test result--- Test Summary: CheckPatch FAIL 0.60 seconds GitLint FAIL 0.12 seconds BuildKernel PASS 665.41 seconds TestRunner: Setup PASS 434.38 seconds TestRunner: l2cap-tester PASS 3.12 seconds TestRunner: bnep-tester PASS 2.10 seconds TestRunner: mgmt-tester PASS 32.77 seconds TestRunner: rfcomm-tester PASS 2.41 seconds TestRunner: sco-tester PASS 2.33 seconds TestRunner: smp-tester PASS 2.45 seconds TestRunner: userchan-tester PASS 2.24 seconds Details ############################## Test: CheckPatch - FAIL - 0.60 seconds Run checkpatch.pl script with rule in .checkpatch.conf Bluetooth: SMP: Fix crash when receiving new connection when debug is enabled WARNING: Unknown commit id '2e1614f7d61e4', maybe rebased or not pulled? #11: Fixes: 2e1614f7d61e4 ("Bluetooth: SMP: Convert BT_ERR/BT_DBG to bt_dev_err/bt_dev_dbg") total: 0 errors, 1 warnings, 0 checks, 16 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: SMP: Fix crash when receiving new connection when" 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: SMP: Fix crash when receiving new connection when debug is enabled 1: T1 Title exceeds max length (77>72): "Bluetooth: SMP: Fix crash when receiving new connection when debug is enabled" 7: B1 Line exceeds max length (87>80): "Fixes: 2e1614f7d61e4 ("Bluetooth: SMP: Convert BT_ERR/BT_DBG to bt_dev_err/bt_dev_dbg")" ############################## Test: BuildKernel - PASS - 665.41 seconds Build Kernel with minimal configuration supports Bluetooth ############################## Test: TestRunner: Setup - PASS - 434.38 seconds Setup environment for running Test Runner ############################## Test: TestRunner: l2cap-tester - PASS - 3.12 seconds Run test-runner with l2cap-tester Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: bnep-tester - PASS - 2.10 seconds Run test-runner with bnep-tester Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: mgmt-tester - PASS - 32.77 seconds Run test-runner with mgmt-tester Total: 446, Passed: 433 (97.1%), Failed: 0, Not Run: 13 ############################## Test: TestRunner: rfcomm-tester - PASS - 2.41 seconds Run test-runner with rfcomm-tester Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: sco-tester - PASS - 2.33 seconds Run test-runner with sco-tester Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: smp-tester - PASS - 2.45 seconds Run test-runner with smp-tester Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: userchan-tester - PASS - 2.24 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
