From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, dev@deq.rocks
Subject: RE: Bluetooth: hci_bcm4377: resume after ACPI S3
Date: Sat, 07 Nov 2026 11:36:00 -0800 (PST) [thread overview]
Message-ID: <6aef7da0.3a67f976.1a5ced.5b23@mx.google.com> (raw)
In-Reply-To: <20261107154839.89941-2-dev@deq.rocks>
[-- Attachment #1: Type: text/plain, Size: 1323 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/1204959/
---Test result---
Test Summary:
CheckPatch PASS 1.21 seconds
VerifyFixes PASS 0.10 seconds
VerifySignedoff PASS 0.11 seconds
GitLint FAIL 0.55 seconds
SubjectPrefix PASS 0.19 seconds
BuildKernel PASS 24.41 seconds
CheckAllWarning PASS 27.70 seconds
CheckSparse PASS 32.92 seconds
BuildKernel32 PASS 23.90 seconds
CheckKernelLLVM PASS 25.36 seconds
TestRunnerSetup PASS 566.09 seconds
IncrementalBuild PASS 24.43 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[1/2] Bluetooth: hci_bcm4377: treat only negative hci_register_dev() returns as errors
1: T1 Title exceeds max length (86>80): "[1/2] Bluetooth: hci_bcm4377: treat only negative hci_register_dev() returns as errors"
https://github.com/bluez/bluetooth-next/pull/1086
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-07 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 15:48 [PATCH 0/2] Bluetooth: hci_bcm4377: resume after ACPI S3 Andre Eikmeyer
2026-11-07 15:48 ` [PATCH 1/2] Bluetooth: hci_bcm4377: treat only negative hci_register_dev() returns as errors Andre Eikmeyer
2026-11-07 19:36 ` bluez.test.bot [this message]
2026-11-08 13:14 ` Sven Peter
2026-11-07 15:48 ` [PATCH 2/2] Bluetooth: hci_bcm4377: probe again after a resume through firmware Andre Eikmeyer
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=6aef7da0.3a67f976.1a5ced.5b23@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=dev@deq.rocks \
--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