From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, runyu.xiao@seu.edu.cn
Subject: RE: Bluetooth: L2CAP: cancel pending_rx_work before taking conn->lock
Date: Wed, 17 Jun 2026 11:04:29 -0700 (PDT) [thread overview]
Message-ID: <6a32e1ad.a3ff9ca7.2f37ba.e7f9@mx.google.com> (raw)
In-Reply-To: <20260617153613.1139031-1-runyu.xiao@seu.edu.cn>
[-- Attachment #1: Type: text/plain, Size: 1355 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=1113030
---Test result---
Test Summary:
CheckPatch PASS 0.66 seconds
VerifyFixes PASS 0.46 seconds
VerifySignedoff PASS 0.16 seconds
GitLint PASS 0.28 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 26.65 seconds
CheckAllWarning PASS 29.50 seconds
CheckSparse PASS 27.53 seconds
BuildKernel32 PASS 25.54 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 588.69 seconds
TestRunner_l2cap-tester PENDING 57.76 seconds
IncrementalBuild PASS 24.84 seconds
Details
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
##############################
Test: TestRunner_l2cap-tester - PENDING
Desc: Run l2cap-tester with test-runner
Output:
https://github.com/bluez/bluetooth-next/pull/327
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-06-17 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 15:36 [PATCH] Bluetooth: L2CAP: cancel pending_rx_work before taking conn->lock Runyu Xiao
2026-06-17 18:04 ` 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=6a32e1ad.a3ff9ca7.2f37ba.e7f9@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=runyu.xiao@seu.edu.cn \
/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