From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ot_zhangchao.zhang@mediatek.com
Subject: RE: Bluetooth: mediatek: add gpio pin to reset bt
Date: Thu, 26 Jun 2025 23:42:18 -0700 (PDT) [thread overview]
Message-ID: <685e3d4a.050a0220.267deb.50b8@mx.google.com> (raw)
In-Reply-To: <20250627055924.7716-2-ot_zhangchao.zhang@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 2463 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=976464
---Test result---
Test Summary:
CheckPatch PENDING 0.33 seconds
GitLint PENDING 0.20 seconds
SubjectPrefix FAIL 0.39 seconds
BuildKernel PASS 24.36 seconds
CheckAllWarning PASS 26.65 seconds
CheckSparse PASS 30.16 seconds
BuildKernel32 PASS 24.13 seconds
TestRunnerSetup PASS 472.21 seconds
TestRunner_l2cap-tester PASS 25.23 seconds
TestRunner_iso-tester PASS 39.91 seconds
TestRunner_bnep-tester PASS 6.01 seconds
TestRunner_mgmt-tester FAIL 135.17 seconds
TestRunner_rfcomm-tester PASS 9.46 seconds
TestRunner_sco-tester PASS 15.03 seconds
TestRunner_ioctl-tester PASS 10.25 seconds
TestRunner_mesh-tester FAIL 11.47 seconds
TestRunner_smp-tester PASS 8.68 seconds
TestRunner_userchan-tester PASS 6.28 seconds
IncrementalBuild PENDING 0.78 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: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 490, Passed: 485 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
LL Privacy - Add Device 3 (AL is full) Failed 0.215 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 2.050 seconds
Mesh - Send cancel - 2 Timed out 1.999 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-06-27 6:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 5:59 [PATCH v5 0/2] Bluetooth: mediatek: add gpio pin to reset bt Zhangchao Zhang
2025-06-27 5:59 ` [PATCH v5 1/2] " Zhangchao Zhang
2025-06-27 6:42 ` bluez.test.bot [this message]
2025-06-27 5:59 ` [PATCH v5 2/2] dt-bindings: net: mediatek,mt7925-bluetooth.yaml Zhangchao Zhang
2025-06-28 12:03 ` Krzysztof Kozlowski
2025-06-28 12:03 ` [PATCH v5 0/2] Bluetooth: mediatek: add gpio pin to reset bt Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2025-09-05 8:40 [PATCH v7 1/1] " Zhangchao Zhang
2025-09-05 8:59 ` bluez.test.bot
2025-07-08 6:01 [PATCH v6 1/1] " Zhangchao Zhang
2025-07-08 6:42 ` bluez.test.bot
2025-06-23 10:23 [PATCH v4 1/1] " Zhangchao Zhang
2025-06-23 11:06 ` bluez.test.bot
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=685e3d4a.050a0220.267deb.50b8@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ot_zhangchao.zhang@mediatek.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.