From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, vulab@iscas.ac.cn
Subject: RE: fix: bluetooth: virtbt_probe: open_failed path calls hci_free_dev instead of hci_unregister_dev
Date: Fri, 26 Jun 2026 06:37:50 -0700 (PDT) [thread overview]
Message-ID: <6a3e80ae.d0999061.a146f.871b@mx.google.com> (raw)
In-Reply-To: <20260626115019.33300-1-vulab@iscas.ac.cn>
[-- Attachment #1: Type: text/plain, Size: 1661 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=1117044
---Test result---
Test Summary:
CheckPatch PASS 1.27 seconds
VerifyFixes PASS 0.24 seconds
VerifySignedoff PASS 0.25 seconds
GitLint FAIL 0.68 seconds
SubjectPrefix FAIL 0.32 seconds
BuildKernel PASS 24.95 seconds
CheckAllWarning PASS 27.29 seconds
CheckSparse PASS 26.40 seconds
BuildKernel32 PASS 23.83 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 449.87 seconds
IncrementalBuild PASS 23.67 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
fix: bluetooth: virtbt_probe: open_failed path calls hci_free_dev instead of hci_unregister_dev
1: T1 Title exceeds max length (95>80): "fix: bluetooth: virtbt_probe: open_failed path calls hci_free_dev instead of hci_unregister_dev"
##############################
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
https://github.com/bluez/bluetooth-next/pull/356
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-06-26 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 11:50 [PATCH] fix: bluetooth: virtbt_probe: open_failed path calls hci_free_dev instead of hci_unregister_dev WenTao Liang
2026-06-26 13:37 ` 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=6a3e80ae.d0999061.a146f.871b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vulab@iscas.ac.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