From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, caiyu7372@gmail.com
Subject: RE: Bluetooth: hci_intel: support the CcP controller (X1 Fold Gen1)
Date: Fri, 25 Sep 2026 18:11:17 -0700 (PDT) [thread overview]
Message-ID: <6ab71bb5.99d0dbd8.144d65.00ca@mx.google.com> (raw)
In-Reply-To: <20260925234043.707679-2-caiyu7372@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1019 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/1174141/
---Test result---
Test Summary:
CheckPatch PASS 2.74 seconds
VerifyFixes PASS 0.11 seconds
VerifySignedoff PASS 0.11 seconds
GitLint PASS 1.20 seconds
SubjectPrefix PASS 0.41 seconds
BuildKernel PASS 27.88 seconds
CheckAllWarning PASS 31.58 seconds
CheckSparse PASS 34.51 seconds
BuildKernel32 PASS 28.01 seconds
CheckKernelLLVM PASS 33.04 seconds
TestRunnerSetup PASS 722.80 seconds
IncrementalBuild PASS 32.88 seconds
https://github.com/bluez/bluetooth-next/pull/821
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-26 1:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 23:40 [RFC PATCH 0/4] Bluetooth: hci_intel: support the CcP controller (X1 Fold Gen1) Cai Yu
2026-09-25 23:40 ` [RFC PATCH 1/4] Bluetooth: hci_intel: fix tty-only assumptions in the LPM paths Cai Yu
2026-09-26 1:11 ` bluez.test.bot [this message]
2026-09-25 23:40 ` [RFC PATCH 2/4] Bluetooth: hci_intel: add the CcP controller (hardware variant 0x14) Cai Yu
2026-09-25 23:40 ` [RFC PATCH 3/4] Bluetooth: hci_intel: add serdev support for the CcP controller Cai Yu
2026-09-25 23:40 ` [RFC PATCH 4/4] Bluetooth: hci_intel: download the CcP firmware at 921.6 kbaud Cai Yu
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=6ab71bb5.99d0dbd8.144d65.00ca@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=caiyu7372@gmail.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