Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, haoxiang_li2024@163.com
Subject: RE: Bluetooth: virtio_bt: unregister HCI device on open failure
Date: Wed, 24 Jun 2026 04:57:22 -0700 (PDT)	[thread overview]
Message-ID: <6a3bc622.a151105c.1c00b1.7ede@mx.google.com> (raw)
In-Reply-To: <20260624084333.2885144-1-haoxiang_li2024@163.com>

[-- Attachment #1: Type: text/plain, Size: 1181 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=1115809

---Test result---

Test Summary:
CheckPatch                    PASS      0.77 seconds
VerifyFixes                   PASS      0.27 seconds
VerifySignedoff               PASS      0.17 seconds
GitLint                       PASS      0.47 seconds
SubjectPrefix                 PASS      0.20 seconds
BuildKernel                   PASS      20.84 seconds
CheckAllWarning               PASS      23.20 seconds
CheckSparse                   PASS      31.01 seconds
BuildKernel32                 PASS      20.39 seconds
CheckKernelLLVM               SKIP      0.00 seconds
TestRunnerSetup               PASS      414.24 seconds
IncrementalBuild              PASS      19.89 seconds

Details
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found


https://github.com/bluez/bluetooth-next/pull/346

---
Regards,
Linux Bluetooth


      parent reply	other threads:[~2026-06-24 11:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-24  8:43 [PATCH] Bluetooth: virtio_bt: unregister HCI device on open failure Haoxiang Li
2026-06-24  9:10 ` Paul Menzel
2026-06-24 10:56 ` Dan Carpenter
2026-06-24 11:57 ` 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=6a3bc622.a151105c.1c00b1.7ede@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=haoxiang_li2024@163.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