From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, chris.lu@mediatek.com
Subject: RE: [RESEND,v1] Bluetooth: btusb: MT7922: Add VID/PID 0489/e174
Date: Thu, 29 Jan 2026 23:36:03 -0800 (PST) [thread overview]
Message-ID: <697c5f63.050a0220.280031.86a3@mx.google.com> (raw)
In-Reply-To: <20260130061356.2343346-1-chris.lu@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 3773 bytes --]
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=1048839
---Test result---
Test Summary:
CheckPatch PENDING 0.43 seconds
GitLint PENDING 0.27 seconds
SubjectPrefix PASS 0.06 seconds
BuildKernel PASS 26.83 seconds
CheckAllWarning PASS 28.82 seconds
CheckSparse WARNING 31.94 seconds
BuildKernel32 PASS 26.33 seconds
TestRunnerSetup PASS 559.30 seconds
TestRunner_l2cap-tester PASS 28.52 seconds
TestRunner_iso-tester FAIL 77.64 seconds
TestRunner_bnep-tester PASS 6.54 seconds
TestRunner_mgmt-tester FAIL 115.57 seconds
TestRunner_rfcomm-tester PASS 9.64 seconds
TestRunner_sco-tester FAIL 14.62 seconds
TestRunner_ioctl-tester PASS 10.55 seconds
TestRunner_mesh-tester FAIL 12.47 seconds
TestRunner_smp-tester PASS 8.54 seconds
TestRunner_userchan-tester PASS 7.34 seconds
IncrementalBuild PENDING 0.81 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
drivers/bluetooth/btusb.c:4659:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4660:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4662:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4663:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4665:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4666:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4668:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4669:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4671:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4672:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4673:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4674:1: error: bad constant expressiondrivers/bluetooth/btusb.c:4674:1: error: bad constant expression
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
BUG: KASAN: slab-use-after-free in le_read_features_complete+0x7e/0x2b0
Total: 141, Passed: 141 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.108 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
BUG: sleeping function called from invalid context at net/core/sock.c:3782
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
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 2.740 seconds
Mesh - Send cancel - 2 Timed out 1.992 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-01-30 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 6:13 [PATCH RESEND v1] Bluetooth: btusb: MT7922: Add VID/PID 0489/e174 Chris Lu
2026-01-30 7:36 ` bluez.test.bot [this message]
2026-02-03 21:34 ` patchwork-bot+bluetooth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=697c5f63.050a0220.280031.86a3@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=chris.lu@mediatek.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox