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=488127 ---Test result--- Test Summary: CheckPatch FAIL 0.71 seconds GitLint PASS 0.14 seconds BuildKernel PASS 707.03 seconds TestRunner: Setup PASS 452.77 seconds TestRunner: l2cap-tester PASS 3.24 seconds TestRunner: bnep-tester PASS 2.24 seconds TestRunner: mgmt-tester PASS 31.55 seconds TestRunner: rfcomm-tester PASS 2.57 seconds TestRunner: sco-tester PASS 2.49 seconds TestRunner: smp-tester PASS 2.56 seconds TestRunner: userchan-tester PASS 2.28 seconds Details ############################## Test: CheckPatch - FAIL - 0.71 seconds Run checkpatch.pl script with rule in .checkpatch.conf Bluetooth: fix the erroneous flush_work() order WARNING: Invalid email format for stable: 'stable <stable@xxxxxxxxxxxxxxx>', prefer 'stable@xxxxxxxxxxxxxxx' #26: Cc: stable <stable@xxxxxxxxxxxxxxx> WARNING: networking block comments don't use an empty /* line, use /* Comment... #39: FILE: net/bluetooth/hci_core.c:1614: + /* + * Since hci_rx_work() is possible to awake new cmd_work WARNING: From:/Signed-off-by: email name mismatch: 'From: linma <linma@xxxxxxxxxx>' != 'Signed-off-by: Lin Ma <linma@xxxxxxxxxx>' total: 0 errors, 3 warnings, 0 checks, 14 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 the erroneous flush_work() order" 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.14 seconds Run gitlint with rule in .gitlint ############################## Test: BuildKernel - PASS - 707.03 seconds Build Kernel with minimal configuration supports Bluetooth ############################## Test: TestRunner: Setup - PASS - 452.77 seconds Setup environment for running Test Runner ############################## Test: TestRunner: l2cap-tester - PASS - 3.24 seconds Run test-runner with l2cap-tester Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: bnep-tester - PASS - 2.24 seconds Run test-runner with bnep-tester Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: mgmt-tester - PASS - 31.55 seconds Run test-runner with mgmt-tester Total: 427, Passed: 412 (96.5%), Failed: 0, Not Run: 15 ############################## Test: TestRunner: rfcomm-tester - PASS - 2.57 seconds Run test-runner with rfcomm-tester Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: sco-tester - PASS - 2.49 seconds Run test-runner with sco-tester Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: smp-tester - PASS - 2.56 seconds Run test-runner with smp-tester Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: userchan-tester - PASS - 2.28 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
