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=492897 ---Test result--- Test Summary: CheckPatch FAIL 6.86 seconds GitLint PASS 0.51 seconds BuildKernel PASS 516.98 seconds TestRunner: Setup PASS 339.79 seconds TestRunner: l2cap-tester PASS 2.46 seconds TestRunner: bnep-tester PASS 1.86 seconds TestRunner: mgmt-tester PASS 27.77 seconds TestRunner: rfcomm-tester PASS 2.03 seconds TestRunner: sco-tester PASS 2.02 seconds TestRunner: smp-tester PASS 2.07 seconds TestRunner: userchan-tester PASS 1.87 seconds Details ############################## Test: CheckPatch - FAIL - 6.86 seconds Run checkpatch.pl script with rule in .checkpatch.conf Bluetooth: eir: Move EIR/Adv Data functions to its own file WARNING: added, moved or deleted file(s), does MAINTAINERS need updating? #82: new file mode 100644 total: 0 errors, 1 warnings, 0 checks, 1069 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: eir: Move EIR/Adv Data functions to its own file" has style problems, please review. NOTE: If any of the errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS. Bluetooth: hci_sync: Make use of hci_cmd_sync_queue set 1 WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line) #17: Set Device Class - Success 1 Passed 0.024 seconds WARNING: added, moved or deleted file(s), does MAINTAINERS need updating? #215: new file mode 100644 total: 0 errors, 2 warnings, 0 checks, 657 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_sync: Make use of hci_cmd_sync_queue set 1" has style problems, please review. NOTE: If any of the errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS. Bluetooth: hci_sync: Make use of hci_cmd_sync_queue set 2 WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line) #17: Add Advertising - Failure: LE off Passed 0.175 seconds CHECK: Alignment should match open parenthesis #400: FILE: net/bluetooth/hci_sync.c:453: + err = __hci_cmd_sync_status(hdev, HCI_OP_LE_SET_EXT_ADV_PARAMS, + sizeof(cp), &cp, HCI_CMD_TIMEOUT); total: 0 errors, 1 warnings, 1 checks, 1381 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_sync: Make use of hci_cmd_sync_queue set 2" has style problems, please review. NOTE: If any of the errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS. Bluetooth: hci_sync: Make use of hci_cmd_sync_queue set 3 WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line) #17: Add Device - Invalid Params 1 Passed 0.016 seconds CHECK: Alignment should match open parenthesis #463: FILE: net/bluetooth/hci_sync.c:1328: +static int hci_le_set_scan_param_sync(struct hci_dev *hdev, u8 type, + u16 interval, u16 window, total: 0 errors, 1 warnings, 1 checks, 660 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_sync: Make use of hci_cmd_sync_queue set 3" 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.51 seconds Run gitlint with rule in .gitlint ############################## Test: BuildKernel - PASS - 516.98 seconds Build Kernel with minimal configuration supports Bluetooth ############################## Test: TestRunner: Setup - PASS - 339.79 seconds Setup environment for running Test Runner ############################## Test: TestRunner: l2cap-tester - PASS - 2.46 seconds Run test-runner with l2cap-tester Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: bnep-tester - PASS - 1.86 seconds Run test-runner with bnep-tester Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: mgmt-tester - PASS - 27.77 seconds Run test-runner with mgmt-tester Total: 446, Passed: 431 (96.6%), Failed: 0, Not Run: 15 ############################## Test: TestRunner: rfcomm-tester - PASS - 2.03 seconds Run test-runner with rfcomm-tester Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: sco-tester - PASS - 2.02 seconds Run test-runner with sco-tester Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: smp-tester - PASS - 2.07 seconds Run test-runner with smp-tester Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0 ############################## Test: TestRunner: userchan-tester - PASS - 1.87 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
