From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, johannes.goede@oss.qualcomm.com
Subject: RE: serdev: ttyport: Clear serport->tty after freeing
Date: Wed, 19 Aug 2026 06:53:05 -0700 (PDT) [thread overview]
Message-ID: <6a85b541.60a87ef9.1b030c.7700@mx.google.com> (raw)
In-Reply-To: <20260819125748.194377-1-johannes.goede@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 2556 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=1148478
---Test result---
Test Summary:
CheckPatch PASS 0.52 seconds
VerifyFixes PASS 0.11 seconds
VerifySignedoff PASS 0.10 seconds
GitLint PASS 0.25 seconds
SubjectPrefix FAIL 0.10 seconds
BuildKernel PASS 18.72 seconds
CheckAllWarning PASS 21.80 seconds
CheckSparse PASS 19.98 seconds
BuildKernel32 PASS 17.30 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 311.28 seconds
TestRunner_l2cap-tester PASS 52.41 seconds
TestRunner_iso-tester PASS 60.32 seconds
TestRunner_bnep-tester PASS 13.37 seconds
TestRunner_mgmt-tester FAIL 184.01 seconds
TestRunner_rfcomm-tester PASS 18.32 seconds
TestRunner_sco-tester PASS 24.48 seconds
TestRunner_ioctl-tester PASS 20.20 seconds
TestRunner_mesh-tester FAIL 19.39 seconds
TestRunner_smp-tester PASS 18.21 seconds
TestRunner_userchan-tester PASS 14.49 seconds
TestRunner_6lowpan-tester PASS 16.63 seconds
IncrementalBuild PASS 18.44 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
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: 501, Passed: 496 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.195 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 1.937 seconds
Mesh - Send cancel - 2 Timed out 1.990 seconds
https://github.com/bluez/bluetooth-next/pull/617
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-08-19 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 12:57 [PATCH] serdev: ttyport: Clear serport->tty after freeing Hans de Goede
2026-08-19 13:53 ` bluez.test.bot [this message]
2026-08-19 16:44 ` Markus Probst
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=6a85b541.60a87ef9.1b030c.7700@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=johannes.goede@oss.qualcomm.com \
--cc=linux-bluetooth@vger.kernel.org \
/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