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=544279 ---Test result--- Test Summary: CheckPatch FAIL 0.61 seconds GitLint FAIL 0.14 seconds BuildKernel PASS 658.30 seconds TestRunner: Setup PASS 438.18 seconds TestRunner: l2cap-tester PASS 3.15 seconds TestRunner: bnep-tester PASS 2.12 seconds TestRunner: mgmt-tester FAIL 34.97 seconds TestRunner: rfcomm-tester PASS 2.49 seconds TestRunner: sco-tester PASS 2.52 seconds TestRunner: smp-tester PASS 2.51 seconds TestRunner: userchan-tester PASS 2.25 seconds Details ############################## Test: CheckPatch - FAIL - 0.61 seconds Run checkpatch.pl script with rule in .checkpatch.conf Bluetooth: btintel: check the correct variable in btintel_get_codec_config_data() WARNING: Unknown commit id '70dd978952bc', maybe rebased or not pulled? #9: Fixes: 70dd978952bc ("Bluetooth: btintel: Define a callback to fetch codec config data") total: 0 errors, 1 warnings, 8 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: btintel: check the correct variable in" 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.14 seconds Run gitlint with rule in .gitlint Bluetooth: btintel: check the correct variable in btintel_get_codec_config_data() 1: T1 Title exceeds max length (81>72): "Bluetooth: btintel: check the correct variable in btintel_get_codec_config_data()" 5: B1 Line exceeds max length (88>80): "Fixes: 70dd978952bc ("Bluetooth: btintel: Define a callback to fetch codec config data")" ############################## Test: BuildKernel - PASS - 658.30 seconds Build Kernel with minimal configuration supports Bluetooth ############################## Test: TestRunner: Setup - PASS - 438.18 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.12 seconds Run test-runner with bnep-tester Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: mgmt-tester - FAIL - 34.97 seconds Run test-runner with mgmt-tester Total: 452, Passed: 451 (99.8%), Failed: 1, Not Run: 0 Failed Test Cases Read Exp Feature - Success Failed 0.017 seconds ############################## Test: TestRunner: rfcomm-tester - PASS - 2.49 seconds Run test-runner with rfcomm-tester Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: sco-tester - PASS - 2.52 seconds Run test-runner with sco-tester Total: 11, Passed: 11 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: smp-tester - PASS - 2.51 seconds Run test-runner with smp-tester Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: userchan-tester - PASS - 2.25 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
