From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zzzccc427@gmail.com
Subject: RE: Bluetooth: hci_sync: Serialize devcoredump reset during device open
Date: Tue, 06 Oct 2026 08:30:04 -0700 (PDT) [thread overview]
Message-ID: <6ac513fc.bd18b5f5.392000.0e25@mx.google.com> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0250-v3-f85e5bae9c76348c88b7@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2381 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/series/1180369/
---Test result---
Test Summary:
CheckPatch PASS 0.74 seconds
VerifyFixes PASS 0.12 seconds
VerifySignedoff PASS 0.12 seconds
GitLint FAIL 0.33 seconds
SubjectPrefix PASS 0.12 seconds
BuildKernel PASS 30.24 seconds
CheckAllWarning PASS 36.40 seconds
CheckSparse PASS 36.59 seconds
BuildKernel32 PASS 29.93 seconds
CheckKernelLLVM PASS 35.37 seconds
TestRunnerSetup PASS 792.81 seconds
TestRunner_l2cap-tester PASS 12.86 seconds
TestRunner_iso-tester PASS 10.73 seconds
TestRunner_bnep-tester PASS 3.14 seconds
TestRunner_mgmt-tester FAIL 72.19 seconds
TestRunner_rfcomm-tester PASS 4.53 seconds
TestRunner_sco-tester PASS 5.63 seconds
TestRunner_ioctl-tester PASS 4.89 seconds
TestRunner_mesh-tester PASS 5.52 seconds
TestRunner_smp-tester PASS 6.99 seconds
TestRunner_userchan-tester PASS 3.20 seconds
TestRunner_6lowpan-tester PASS 4.42 seconds
IncrementalBuild PASS 28.76 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: hci_sync: Serialize devcoredump reset during device open
40: B2 Line has trailing whitespace: " "
41: B2 Line has trailing whitespace: " CPU: 0 UID: 0 PID: 496 Comm: kworker/u17:0 Not tainted "
42: B2 Line has trailing whitespace: " 7.2.0-rc6-pmb-bt-functional-v1+ #1 PREEMPT(lazy) "
43: B2 Line has trailing whitespace: " Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps "
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 503, Passed: 502 (99.8%), Failed: 1, Not Run: 0
Failed Test Cases
Pairing Acceptor - SMP over BR/EDR 2 Timed out 2.481 seconds
https://github.com/bluez/bluetooth-next/pull/870
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-06 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 14:39 [PATCH] Bluetooth: hci_sync: Serialize devcoredump reset during device open Cen Zhang
2026-10-06 15:30 ` bluez.test.bot [this message]
2026-10-07 17:30 ` 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=6ac513fc.bd18b5f5.392000.0e25@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zzzccc427@gmail.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