RE: USB/Bluetooth: recover MT7925 after warm reboot

[email protected]
Newsgroups org.kernel.vger.linux-bluetooth
Message-ID <[email protected]>
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=1147517

---Test result---

Test Summary:
CheckPatch                    FAIL      1.94 seconds
VerifyFixes                   PASS      0.14 seconds
VerifySignedoff               PASS      0.14 seconds
GitLint                       FAIL      0.66 seconds
SubjectPrefix                 FAIL      0.26 seconds
BuildKernel                   PASS      27.45 seconds
CheckAllWarning               PASS      30.18 seconds
CheckSparse                   PASS      28.91 seconds
BuildKernel32                 PASS      26.45 seconds
CheckKernelLLVM               SKIP      0.00 seconds
TestRunnerSetup               PASS      504.88 seconds
TestRunner_l2cap-tester       PASS      66.18 seconds
TestRunner_iso-tester         PASS      81.14 seconds
TestRunner_bnep-tester        PASS      19.30 seconds
TestRunner_mgmt-tester        FAIL      225.09 seconds
TestRunner_rfcomm-tester      PASS      25.60 seconds
TestRunner_sco-tester         PASS      32.45 seconds
TestRunner_ioctl-tester       PASS      26.93 seconds
TestRunner_mesh-tester        FAIL      25.95 seconds
TestRunner_smp-tester         PASS      23.96 seconds
TestRunner_userchan-tester    PASS      20.87 seconds
TestRunner_6lowpan-tester     PASS      23.51 seconds
IncrementalBuild              PASS      27.95 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[RFC,2/2] Bluetooth: mt7925: recover subsystem-reset timeout through USB re-enumeration
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#114: 
  Bluetooth: hci0: MT7925 WMT func ctrl timed out (dev_id=0x7925), scheduling device reset

total: 0 errors, 1 warnings, 32 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/patch/14754479.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: GitLint - FAIL
Desc: Run gitlint
Output:
[RFC,2/2] Bluetooth: mt7925: recover subsystem-reset timeout through USB re-enumeration

1: T1 Title exceeds max length (87>80): "[RFC,2/2] Bluetooth: mt7925: recover subsystem-reset timeout through USB re-enumeration"
36: B1 Line exceeds max length (90>80): "  Bluetooth: hci0: MT7925 WMT func ctrl timed out (dev_id=0x7925), scheduling device reset"
76: B1 Line exceeds max length (82>80): "  Bluetooth: hci0: MT7925 subsystem reset timed out, requesting USB re-enumeration"
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 501, Passed: 496 (99.0%), Failed: 1, Not Run: 4

Failed Test Cases
Read Exp Feature - Success                           Failed       0.254 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0

Failed Test Cases
Mesh - Send cancel - 1                               Timed out    1.995 seconds
Mesh - Send cancel - 2                               Timed out    1.990 seconds


https://github.com/bluez/bluetooth-next/pull/604

---
Regards,
Linux Bluetooth
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.