From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, enghitalo@gmail.com
Subject: RE: Bluetooth: Fix SCO setup failures after an abandoned setup
Date: Thu, 08 Oct 2026 18:11:40 -0700 (PDT) [thread overview]
Message-ID: <6ac83f4c.a4ef0faa.3cd013.f020@mx.google.com> (raw)
In-Reply-To: <20261008222616.2780570-2-enghitalo@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3600 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/1181908/
---Test result---
Test Summary:
CheckPatch FAIL 4.68 seconds
VerifyFixes PASS 0.12 seconds
VerifySignedoff PASS 0.13 seconds
GitLint FAIL 2.01 seconds
SubjectPrefix PASS 0.72 seconds
BuildKernel PASS 29.53 seconds
CheckAllWarning PASS 33.73 seconds
CheckSparse WARNING 37.15 seconds
BuildKernel32 PASS 29.38 seconds
CheckKernelLLVM PASS 35.39 seconds
TestRunnerSetup PASS 779.04 seconds
TestRunner_l2cap-tester PASS 12.84 seconds
TestRunner_iso-tester PASS 17.07 seconds
TestRunner_bnep-tester PASS 3.11 seconds
TestRunner_mgmt-tester PASS 61.19 seconds
TestRunner_rfcomm-tester PASS 4.49 seconds
TestRunner_sco-tester PASS 5.38 seconds
TestRunner_ioctl-tester PASS 4.64 seconds
TestRunner_mesh-tester PASS 5.51 seconds
TestRunner_smp-tester PASS 4.36 seconds
TestRunner_userchan-tester PASS 3.19 seconds
TestRunner_6lowpan-tester PASS 4.41 seconds
IncrementalBuild PASS 54.47 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v3,1/6] Bluetooth: hci_event: Don't fail a connected SCO link on setup errors
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit a13f316e90fd ("Bluetooth: hci_conn: Consolidate code for aborting connections")'
#111:
A link that is up can be the first one on the ACL since commit
total: 1 errors, 0 warnings, 0 checks, 44 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14875449.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v3,3/6] Bluetooth: hci_event: Disconnect links that complete while being aborted
1: T1 Title exceeds max length (81>80): "[v3,3/6] Bluetooth: hci_event: Disconnect links that complete while being aborted"
[v3,5/6] Bluetooth: hci_event: Disconnect an ACL link that completes after its abort
1: T1 Title exceeds max length (84>80): "[v3,5/6] Bluetooth: hci_event: Disconnect an ACL link that completes after its abort"
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
https://github.com/bluez/bluetooth-next/pull/891
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-09 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 22:26 [PATCH v3 0/6] Bluetooth: Fix SCO setup failures after an abandoned setup Hitalo Souza
2026-10-08 22:26 ` [PATCH v3 1/6] Bluetooth: hci_event: Don't fail a connected SCO link on setup errors Hitalo Souza
2026-10-09 1:11 ` bluez.test.bot [this message]
2026-10-08 22:26 ` [PATCH v3 2/6] Bluetooth: hci_conn: Don't set up a SCO link that is already up Hitalo Souza
2026-10-08 22:26 ` [PATCH v3 3/6] Bluetooth: hci_event: Disconnect links that complete while being aborted Hitalo Souza
2026-10-08 22:26 ` [PATCH v3 4/6] Bluetooth: Don't leave abandoned SCO links up in the controller Hitalo Souza
2026-10-08 22:26 ` [PATCH v3 5/6] Bluetooth: hci_event: Disconnect an ACL link that completes after its abort Hitalo Souza
2026-10-08 22:26 ` [PATCH v3 6/6] Bluetooth: hci_event: Notify the driver only of SCO links that came up Hitalo Souza
2026-10-09 13:57 ` [PATCH v3 0/6] Bluetooth: Fix SCO setup failures after an abandoned setup Luiz Augusto von Dentz
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=6ac83f4c.a4ef0faa.3cd013.f020@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=enghitalo@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