RE: [v6] Bluetooth: Scrub MGMT cmd pending queue for consistency

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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=619336

---Test result---

Test Summary:
CheckPatch                    FAIL      1.49 seconds
GitLint                       PASS      0.83 seconds
SubjectPrefix                 PASS      0.69 seconds
BuildKernel                   PASS      35.30 seconds
BuildKernel32                 PASS      30.88 seconds
Incremental Build with patchesPASS      42.61 seconds
TestRunner: Setup             PASS      553.01 seconds
TestRunner: l2cap-tester      PASS      14.93 seconds
TestRunner: bnep-tester       PASS      6.76 seconds
TestRunner: mgmt-tester       PASS      115.32 seconds
TestRunner: rfcomm-tester     FAIL      8.45 seconds
TestRunner: sco-tester        PASS      8.53 seconds
TestRunner: smp-tester        PASS      8.56 seconds
TestRunner: userchan-tester   PASS      7.31 seconds

Details
##############################
Test: CheckPatch - FAIL - 1.49 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
[v6] Bluetooth: Scrub MGMT cmd pending queue for consistency\CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#274: FILE: net/bluetooth/mgmt.c:5291:
+	if (cmd != pending_find(MGMT_OP_START_DISCOVERY, hdev) &&
+		cmd != pending_find(MGMT_OP_START_LIMITED_DISCOVERY, hdev) &&

total: 0 errors, 0 warnings, 1 checks, 275 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/12765234.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 - 8.45 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.171 seconds



---
Regards,
Linux Bluetooth


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux