From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zijun.hu@oss.qualcomm.com
Subject: RE: Bluetooth: btusb: Preparation for upcoming Qualcomm QCC2072 support
Date: Thu, 09 Jul 2026 02:29:11 -0700 (PDT) [thread overview]
Message-ID: <6a4f69e7.4aa243c6.1c4077.e83d@mx.google.com> (raw)
In-Reply-To: <20260708-btusb_prep_qcc2072-v1-1-d835b187fd01@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 3126 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=1124323
---Test result---
Test Summary:
CheckPatch FAIL 14.94 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint PASS 1.98 seconds
SubjectPrefix PASS 0.78 seconds
BuildKernel PASS 26.94 seconds
CheckAllWarning PASS 29.49 seconds
CheckSparse PASS 29.35 seconds
BuildKernel32 PASS 27.22 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 505.63 seconds
TestRunner_l2cap-tester PASS 60.98 seconds
TestRunner_iso-tester PASS 87.99 seconds
TestRunner_bnep-tester PASS 19.11 seconds
TestRunner_mgmt-tester FAIL 216.23 seconds
TestRunner_rfcomm-tester PASS 25.43 seconds
TestRunner_sco-tester PASS 32.82 seconds
TestRunner_ioctl-tester PASS 26.48 seconds
TestRunner_mesh-tester FAIL 25.93 seconds
TestRunner_smp-tester PASS 23.21 seconds
TestRunner_userchan-tester PASS 20.16 seconds
TestRunner_6lowpan-tester PASS 22.61 seconds
IncrementalBuild PASS 54.44 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[6/6] Bluetooth: btusb: Build the driver from multiple source files
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#167:
drivers/bluetooth/{btusb.c => btusb_main.c} | 0
total: 0 errors, 1 warnings, 6 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/14674248.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: 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: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.250 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.200 seconds
Mesh - Send cancel - 2 Timed out 1.987 seconds
https://github.com/bluez/bluetooth-next/pull/414
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-07-09 9:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 6:14 [PATCH 0/6] Bluetooth: btusb: Preparation for upcoming Qualcomm QCC2072 support Zijun Hu
2026-07-09 6:14 ` [PATCH 1/6] Bluetooth: coredump: Introduce and apply hci_devcd_state_name() Zijun Hu
2026-07-09 9:29 ` bluez.test.bot [this message]
2026-07-09 6:14 ` [PATCH 2/6] Bluetooth: coredump: Allow drivers to pad dump header to fixed size Zijun Hu
2026-07-09 6:15 ` [PATCH 3/6] Bluetooth: btusb: Add an indirect recv_intr() hook to btusb_data Zijun Hu
2026-07-09 6:15 ` [PATCH 4/6] Bluetooth: btusb: Add wrappers btusb_recv_{event,acl}_hdev() Zijun Hu
2026-07-09 6:15 ` [PATCH 5/6] Bluetooth: btusb: Add a simple static btusb_prepare_reset() Zijun Hu
2026-07-09 6:15 ` [PATCH 6/6] Bluetooth: btusb: Build the driver from multiple source files Zijun Hu
2026-07-09 13:40 ` Luiz Augusto von Dentz
2026-07-09 13:46 ` [PATCH 0/6] Bluetooth: btusb: Preparation for upcoming Qualcomm QCC2072 support Luiz Augusto von Dentz
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=6a4f69e7.4aa243c6.1c4077.e83d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox