From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zijun.hu@oss.qualcomm.com
Subject: RE: Bluetooth: btusb: Support Qualcomm multi-subsystem QCC2072
Date: Sun, 30 Aug 2026 23:41:08 -0700 (PDT) [thread overview]
Message-ID: <6a952204.7b32ee26.e8bf0.8889@mx.google.com> (raw)
In-Reply-To: <20260830-btusb_qcc2072-v2-1-5c0e0c9dd98b@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 4254 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=1154112
---Test result---
Test Summary:
CheckPatch FAIL 7.74 seconds
VerifyFixes PASS 0.08 seconds
VerifySignedoff PASS 0.08 seconds
GitLint FAIL 0.92 seconds
SubjectPrefix PASS 0.32 seconds
BuildKernel PASS 28.98 seconds
CheckAllWarning PASS 31.99 seconds
CheckSparse PASS 30.60 seconds
BuildKernel32 PASS 27.89 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 527.19 seconds
TestRunner_l2cap-tester PASS 71.10 seconds
TestRunner_iso-tester PASS 108.50 seconds
TestRunner_bnep-tester PASS 20.19 seconds
TestRunner_mgmt-tester FAIL 238.88 seconds
TestRunner_rfcomm-tester PASS 27.38 seconds
TestRunner_sco-tester PASS 33.32 seconds
TestRunner_ioctl-tester PASS 27.83 seconds
TestRunner_mesh-tester FAIL 27.18 seconds
TestRunner_smp-tester PASS 25.21 seconds
TestRunner_userchan-tester PASS 20.77 seconds
TestRunner_6lowpan-tester PASS 24.84 seconds
IncrementalBuild PASS 53.54 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2,3/4] Bluetooth: btusb: Build the driver from multiple source files
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#174:
drivers/bluetooth/{btusb.c => btusb_main.c} | 0
total: 0 errors, 1 warnings, 11 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/14776343.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.
[v2,4/4] Bluetooth: btusb: Add support for Qualcomm multi-subsystem QCC2072
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#471:
new file mode 100644
total: 0 errors, 1 warnings, 4812 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/14776345.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:
[v2,4/4] Bluetooth: btusb: Add support for Qualcomm multi-subsystem QCC2072
8: B3 Line contains hard tab characters (\t): " USB I/F | internal link |"
9: B3 Line contains hard tab characters (\t): "BTHOST -------- |---- PERI -------------- BT |"
10: B3 Line contains hard tab characters (\t): " |_______________________________|"
##############################
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: 495 (98.8%), Failed: 2, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.276 seconds
LL Privacy - Unpair 1 Timed out 1.960 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 2.064 seconds
Mesh - Send cancel - 2 Timed out 1.992 seconds
https://github.com/bluez/bluetooth-next/pull/670
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-08-31 6:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 5:03 [PATCH v2 0/4] Bluetooth: btusb: Support Qualcomm multi-subsystem QCC2072 Zijun Hu
2026-08-31 5:03 ` [PATCH v2 1/4] Bluetooth: btusb: Add recv_intr() hook to btusb_data Zijun Hu
2026-08-31 6:41 ` bluez.test.bot [this message]
2026-08-31 5:03 ` [PATCH v2 2/4] Bluetooth: Add generic support for vendor HCI packets Zijun Hu
2026-08-31 14:45 ` Luiz Augusto von Dentz
2026-09-02 10:22 ` Zijun Hu
2026-08-31 5:03 ` [PATCH v2 3/4] Bluetooth: btusb: Build the driver from multiple source files Zijun Hu
2026-08-31 5:03 ` [PATCH v2 4/4] Bluetooth: btusb: Add support for Qualcomm multi-subsystem QCC2072 Zijun Hu
2026-08-31 14:34 ` [PATCH v2 0/4] Bluetooth: btusb: Support " Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2026-09-07 8:45 [PATCH v3 1/4] Bluetooth: btusb: Add recv_intr() hook to btusb_data Zijun Hu
2026-09-07 13:59 ` Bluetooth: btusb: Support Qualcomm multi-subsystem QCC2072 bluez.test.bot
2026-09-08 15:58 ` bluez.test.bot
2026-09-10 14:35 [PATCH v4 1/4] Bluetooth: btusb: Add recv_intr() hook to btusb_data Zijun Hu
2026-09-10 19:01 ` Bluetooth: btusb: Support Qualcomm multi-subsystem QCC2072 bluez.test.bot
2026-09-11 8:00 [PATCH v5 1/4] Bluetooth: btusb: Add recv_intr() hook to btusb_data Zijun Hu
2026-09-11 10:17 ` Bluetooth: btusb: Support Qualcomm multi-subsystem QCC2072 bluez.test.bot
2026-09-14 2:46 [PATCH v6 1/4] Bluetooth: btusb: Add recv_intr() hook to btusb_data Zijun Hu
2026-09-14 6:02 ` Bluetooth: btusb: Support Qualcomm multi-subsystem QCC2072 bluez.test.bot
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=6a952204.7b32ee26.e8bf0.8889@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zijun.hu@oss.qualcomm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.