From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v1] Bluetooth: btintel_pcie: Allow COMPILE_TEST without ACPI
Date: Thu, 22 Oct 2026 11:08:57 -0700 (PDT) [thread overview]
Message-ID: <6ada5139.b31e8986.2e168b.829a@mx.google.com> (raw)
In-Reply-To: <20261022154621.3958803-1-luiz.dentz@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/1191410/
---Test result---
Test Summary:
CheckPatch PASS 2.07 seconds
VerifyFixes PASS 0.11 seconds
VerifySignedoff PASS 0.11 seconds
GitLint PASS 0.49 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 22.64 seconds
CheckAllWarning PASS 20.64 seconds
CheckSparse PASS 23.52 seconds
BuildKernel32 PASS 18.91 seconds
CheckKernelLLVM PASS 21.88 seconds
TestRunnerSetup PASS 435.67 seconds
IncrementalBuild PASS 18.96 seconds
https://github.com/bluez/bluetooth-next/pull/983
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-22 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 15:46 [PATCH v1] Bluetooth: btintel_pcie: Allow COMPILE_TEST without ACPI Luiz Augusto von Dentz
2026-10-22 15:46 ` [PATCH v1] Bluetooth: L2CAP: Hold incoming data until encryption key size is known Luiz Augusto von Dentz
2026-10-22 18:20 ` [v1] " bluez.test.bot
2026-10-23 21:00 ` [PATCH v1] " patchwork-bot+bluetooth
2026-10-22 18:08 ` bluez.test.bot [this message]
2026-10-23 21:00 ` [PATCH v1] Bluetooth: btintel_pcie: Allow COMPILE_TEST without ACPI patchwork-bot+bluetooth
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=6ada5139.b31e8986.2e168b.829a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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