From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zzzccc427@gmail.com
Subject: RE: Bluetooth: hci_debugfs: serialize force_bredr_smp writes
Date: Thu, 18 Jun 2026 06:21:48 -0700 (PDT) [thread overview]
Message-ID: <6a33f0ec.63d39acb.391892.7d5a@mx.google.com> (raw)
In-Reply-To: <20260618102150.3340673-1-zzzccc427@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3165 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=1113387
---Test result---
Test Summary:
CheckPatch FAIL 0.53 seconds
VerifyFixes PASS 0.06 seconds
VerifySignedoff PASS 0.06 seconds
GitLint PASS 0.18 seconds
SubjectPrefix PASS 0.05 seconds
BuildKernel PASS 26.74 seconds
CheckAllWarning PASS 29.66 seconds
CheckSparse PASS 27.99 seconds
BuildKernel32 PASS 25.94 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 581.10 seconds
TestRunner_l2cap-tester PASS 60.19 seconds
TestRunner_iso-tester PASS 79.55 seconds
TestRunner_bnep-tester PASS 18.66 seconds
TestRunner_mgmt-tester FAIL 212.01 seconds
TestRunner_rfcomm-tester PASS 24.97 seconds
TestRunner_sco-tester PASS 32.66 seconds
TestRunner_ioctl-tester PASS 28.46 seconds
TestRunner_mesh-tester FAIL 25.84 seconds
TestRunner_smp-tester PASS 23.43 seconds
TestRunner_userchan-tester PASS 19.82 seconds
TestRunner_6lowpan-tester PASS 22.93 seconds
IncrementalBuild PASS 25.13 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: hci_debugfs: serialize force_bredr_smp writes
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#108:
2. test HCI_FORCE_BREDR_SMP as set 2. test HCI_FORCE_BREDR_SMP as set
total: 0 errors, 1 warnings, 0 checks, 9 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/14635033.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.245 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.549 seconds
Mesh - Send cancel - 2 Timed out 1.982 seconds
https://github.com/bluez/bluetooth-next/pull/332
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-06-18 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 10:21 [PATCH] Bluetooth: hci_debugfs: serialize force_bredr_smp writes Cen Zhang
2026-06-18 13:21 ` bluez.test.bot [this message]
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=6a33f0ec.63d39acb.391892.7d5a@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