From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org,
christian.koever-draxl@student.uibk.ac.at
Subject: RE: Bluetooth: make the Amlogic W1 (W155S2) usable
Date: Sun, 25 Oct 2026 13:18:00 -0700 (PDT) [thread overview]
Message-ID: <6ade63f8.48d69adf.259d3b.4b42@mx.google.com> (raw)
In-Reply-To: <20261025192338.209574-2-christian.koever-draxl@student.uibk.ac.at>
[-- Attachment #1: Type: text/plain, Size: 2120 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/1193155/
---Test result---
Test Summary:
CheckPatch PASS 4.94 seconds
VerifyFixes PASS 0.09 seconds
VerifySignedoff PASS 0.09 seconds
GitLint FAIL 1.87 seconds
SubjectPrefix FAIL 0.60 seconds
BuildKernel PASS 22.55 seconds
CheckAllWarning PASS 25.46 seconds
CheckSparse PASS 28.35 seconds
BuildKernel32 PASS 22.61 seconds
CheckKernelLLVM PASS 26.51 seconds
TestRunnerSetup PASS 520.03 seconds
TestRunner_l2cap-tester PASS 13.41 seconds
TestRunner_iso-tester PASS 9.52 seconds
TestRunner_bnep-tester PASS 2.98 seconds
TestRunner_mgmt-tester PASS 83.76 seconds
TestRunner_rfcomm-tester PASS 4.09 seconds
TestRunner_sco-tester PASS 5.12 seconds
TestRunner_ioctl-tester PASS 4.23 seconds
TestRunner_mesh-tester PASS 5.10 seconds
TestRunner_smp-tester PASS 4.02 seconds
TestRunner_userchan-tester PASS 2.85 seconds
TestRunner_6lowpan-tester PASS 4.13 seconds
IncrementalBuild PASS 42.45 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[1/7] Bluetooth: add a quirk for controllers that cannot enable Secure Connections
1: T1 Title exceeds max length (82>80): "[1/7] Bluetooth: add a quirk for controllers that cannot enable Secure Connections"
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
https://github.com/bluez/bluetooth-next/pull/1002
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-25 20:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 19:23 [PATCH 0/7] Bluetooth: make the Amlogic W1 (W155S2) usable christian.koever-draxl
2026-10-25 19:23 ` [PATCH 1/7] Bluetooth: add a quirk for controllers that cannot enable Secure Connections christian.koever-draxl
2026-10-25 20:08 ` sashiko-bot
2026-10-25 20:18 ` bluez.test.bot [this message]
2026-10-25 19:23 ` [PATCH 2/7] Bluetooth: add a quirk for controllers that hang on Write Current IAC LAP christian.koever-draxl
2026-10-25 19:23 ` [PATCH 3/7] Bluetooth: hci_aml: cope with a controller that is already running christian.koever-draxl
2026-10-25 20:16 ` sashiko-bot
2026-10-25 19:23 ` [PATCH 4/7] dt-bindings: net: bluetooth: amlogic,w155s2-bt: allow local-bd-address christian.koever-draxl
2026-10-25 19:23 ` [PATCH 5/7] Bluetooth: hci_aml: take the address from the firmware description christian.koever-draxl
2026-10-25 19:23 ` [PATCH 6/7] dt-bindings: net: bluetooth: amlogic,w155s2-bt: add amlogic,shared-antenna christian.koever-draxl
2026-10-25 19:23 ` [PATCH 7/7] Bluetooth: hci_aml: configure the RF for a shared antenna christian.koever-draxl
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=6ade63f8.48d69adf.259d3b.4b42@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=christian.koever-draxl@student.uibk.ac.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.