From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, mahesh.talewad@nxp.com
Subject: RE: Enhanced or Legacy Accept Synchronous Connection Request command'
Date: Thu, 30 Oct 2025 07:35:56 -0700 (PDT) [thread overview]
Message-ID: <690377cc.050a0220.3b08f.b78c@mx.google.com> (raw)
In-Reply-To: <20251030134856.2726882-2-mahesh.talewad@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2909 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/project/bluetooth/list/?series=1017750
---Test result---
Test Summary:
CheckPatch PENDING 0.37 seconds
GitLint PENDING 0.27 seconds
SubjectPrefix FAIL 0.37 seconds
BuildKernel PASS 25.87 seconds
CheckAllWarning PASS 28.87 seconds
CheckSparse WARNING 32.58 seconds
BuildKernel32 PASS 25.58 seconds
TestRunnerSetup PASS 513.18 seconds
TestRunner_l2cap-tester PASS 24.58 seconds
TestRunner_iso-tester FAIL 46.16 seconds
TestRunner_bnep-tester PASS 9.27 seconds
TestRunner_mgmt-tester FAIL 124.58 seconds
TestRunner_rfcomm-tester PASS 9.43 seconds
TestRunner_sco-tester PASS 14.56 seconds
TestRunner_ioctl-tester PASS 10.24 seconds
TestRunner_mesh-tester FAIL 11.69 seconds
TestRunner_smp-tester PASS 8.77 seconds
TestRunner_userchan-tester PASS 6.69 seconds
IncrementalBuild PENDING 0.57 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/sco.c: note: in included file:./include/net/bluetooth/hci_core.h:153:35: warning: array of flexible structures
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
No test result found
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 490, Passed: 484 (98.8%), Failed: 2, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.104 seconds
LL Privacy - Add Device 3 (AL is full) Failed 0.184 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 1.926 seconds
Mesh - Send cancel - 2 Timed out 2.001 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-10-30 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 13:48 [PATCH BlueZ v1 0/1] Enhanced or Legacy Accept Synchronous Connection Request command' Mahesh Talewad
2025-10-30 13:48 ` [PATCH BlueZ v1 1/1] When Connect request for eSco is received, if enhanced synchronous connection command is supported it will go for 'Enhanced Accept Synchronous Connection Request command' else it will go for legacy command['Accept Synchronous Connection Request comand'] Mahesh Talewad
2025-10-30 14:04 ` Luiz Augusto von Dentz
2025-10-30 14:35 ` bluez.test.bot [this message]
2025-10-30 14:06 ` [PATCH BlueZ v1 0/1] Enhanced or Legacy Accept Synchronous Connection Request command' 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=690377cc.050a0220.3b08f.b78c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mahesh.talewad@nxp.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 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.