From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zzzccc427@gmail.com
Subject: RE: Bluetooth: hci_core: Keep RCU protection through LTK filtering
Date: Tue, 06 Oct 2026 01:34:12 -0700 (PDT) [thread overview]
Message-ID: <6ac4b284.2c5b8305.142fc5.bce8@mx.google.com> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0123-v5-83023fa5b4741c350341@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3746 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/1180109/
---Test result---
Test Summary:
CheckPatch FAIL 0.55 seconds
VerifyFixes PASS 0.30 seconds
VerifySignedoff PASS 0.10 seconds
GitLint FAIL 0.25 seconds
SubjectPrefix PASS 0.09 seconds
BuildKernel PASS 23.18 seconds
CheckAllWarning PASS 24.83 seconds
CheckSparse PASS 26.94 seconds
BuildKernel32 PASS 22.17 seconds
CheckKernelLLVM PASS 25.81 seconds
TestRunnerSetup PASS 573.55 seconds
TestRunner_l2cap-tester PASS 13.28 seconds
TestRunner_iso-tester PASS 9.32 seconds
TestRunner_bnep-tester PASS 2.79 seconds
TestRunner_mgmt-tester PASS 56.84 seconds
TestRunner_rfcomm-tester PASS 4.06 seconds
TestRunner_sco-tester PASS 5.03 seconds
TestRunner_ioctl-tester PASS 4.18 seconds
TestRunner_mesh-tester FAIL 7.66 seconds
TestRunner_smp-tester PASS 3.99 seconds
TestRunner_userchan-tester PASS 2.86 seconds
TestRunner_6lowpan-tester PASS 3.99 seconds
IncrementalBuild PASS 21.92 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: hci_core: Keep RCU protection through LTK filtering
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#156:
kfence-#249: 0x00000000121f2ad9-0x000000005b5bfb3d, size=72, cache=kmalloc-96
total: 0 errors, 1 warnings, 0 checks, 18 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.
/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14869374.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:
Bluetooth: hci_core: Keep RCU protection through LTK filtering
42: B2 Line has trailing whitespace: " "
55: B2 Line has trailing whitespace: " "
56: B1 Line exceeds max length (81>80): " kfence-#249: 0x00000000121f2ad9-0x000000005b5bfb3d, size=72, cache=kmalloc-96"
57: B2 Line has trailing whitespace: " "
66: B2 Line has trailing whitespace: " "
86: B2 Line has trailing whitespace: " "
87: B1 Line exceeds max length (120>80): " CPU: 1 UID: 0 PID: 495 Comm: python3 Tainted: G O 7.2.0-rc6-pmb-bt-functional-v1+ #1 PREEMPT(lazy) "
87: B2 Line has trailing whitespace: " CPU: 1 UID: 0 PID: 495 Comm: python3 Tainted: G O 7.2.0-rc6-pmb-bt-functional-v1+ #1 PREEMPT(lazy) "
89: B1 Line exceeds max length (119>80): " Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014"
##############################
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.642 seconds
Mesh - Send cancel - 2 Timed out 1.999 seconds
https://github.com/bluez/bluetooth-next/pull/868
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-06 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 7:38 [PATCH] Bluetooth: hci_core: Keep RCU protection through LTK filtering Cen Zhang
2026-10-06 8:34 ` 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=6ac4b284.2c5b8305.142fc5.bce8@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