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=619444 ---Test result--- Test Summary: CheckPatch FAIL 1.66 seconds GitLint PASS 0.99 seconds SubjectPrefix PASS 0.89 seconds BuildKernel PASS 30.15 seconds BuildKernel32 PASS 26.78 seconds Incremental Build with patchesPASS 37.21 seconds TestRunner: Setup PASS 477.73 seconds TestRunner: l2cap-tester PASS 13.67 seconds TestRunner: bnep-tester PASS 6.09 seconds TestRunner: mgmt-tester PASS 105.01 seconds TestRunner: rfcomm-tester FAIL 7.68 seconds TestRunner: sco-tester PASS 7.80 seconds TestRunner: smp-tester PASS 7.68 seconds TestRunner: userchan-tester PASS 6.52 seconds Details ############################## Test: CheckPatch - FAIL - 1.66 seconds Run checkpatch.pl script with rule in .checkpatch.conf [RFC] Bluetooth: hci_sync: Fix not processing all entries on cmd_sync_work\CHECK:LINE_SPACING: Please don't use multiple blank lines #99: FILE: net/bluetooth/hci_sync.c:276: + total: 0 errors, 0 warnings, 1 checks, 82 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. /github/workspace/src/12765538.patch has style problems, please review. NOTE: Ignored message types: UNKNOWN_COMMIT_ID NOTE: If any of the errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS. ############################## Test: TestRunner: rfcomm-tester - FAIL - 7.68 seconds Run test-runner with rfcomm-tester Total: 10, Passed: 9 (90.0%), Failed: 1, Not Run: 0 Failed Test Cases Basic RFCOMM Socket Client - Write 32k Success Failed 0.155 seconds --- Regards, Linux Bluetooth
