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=547637 ---Test result--- Test Summary: CheckPatch FAIL 1.81 seconds GitLint FAIL 0.50 seconds BuildKernel PASS 622.33 seconds TestRunner: Setup PASS 406.20 seconds TestRunner: l2cap-tester PASS 3.03 seconds TestRunner: bnep-tester PASS 2.15 seconds TestRunner: mgmt-tester PASS 32.17 seconds TestRunner: rfcomm-tester PASS 2.29 seconds TestRunner: sco-tester PASS 2.31 seconds TestRunner: smp-tester PASS 2.35 seconds TestRunner: userchan-tester PASS 2.16 seconds Details ############################## Test: CheckPatch - FAIL - 1.81 seconds Run checkpatch.pl script with rule in .checkpatch.conf Bluetooth: Fix passing NULL to PTR_ERR WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line) #7: bt_skb_sendmsg does never return NULL it is safe to replace the instances of total: 0 errors, 1 warnings, 0 checks, 24 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: Fix passing NULL to PTR_ERR" 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.50 seconds Run gitlint with rule in .gitlint Bluetooth: SCO: Fix sco_send_frame returning skb->len 6: B1 Line exceeds max length (90>80): "Fixes: 0771cbb3b97d ("Bluetooth: SCO: Replace use of memcpy_from_msg with bt_skb_sendmsg")" ############################## Test: BuildKernel - PASS - 622.33 seconds Build Kernel with minimal configuration supports Bluetooth ############################## Test: TestRunner: Setup - PASS - 406.20 seconds Setup environment for running Test Runner ############################## Test: TestRunner: l2cap-tester - PASS - 3.03 seconds Run test-runner with l2cap-tester Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: bnep-tester - PASS - 2.15 seconds Run test-runner with bnep-tester Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: mgmt-tester - PASS - 32.17 seconds Run test-runner with mgmt-tester Total: 452, Passed: 452 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: rfcomm-tester - PASS - 2.29 seconds Run test-runner with rfcomm-tester Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: sco-tester - PASS - 2.31 seconds Run test-runner with sco-tester Total: 11, Passed: 11 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: smp-tester - PASS - 2.35 seconds Run test-runner with smp-tester Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: userchan-tester - PASS - 2.16 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
