From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, chris.lu@mediatek.com
Subject: RE: Bluetooth: btmtksdio: ensure btmtksdio_close is executed before btmtksdio_remove
Date: Mon, 21 Apr 2025 20:07:50 -0700 (PDT) [thread overview]
Message-ID: <68070806.170a0220.2dc04e.5251@mx.google.com> (raw)
In-Reply-To: <20250422012156.586600-2-chris.lu@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 1949 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=955503
---Test result---
Test Summary:
CheckPatch PENDING 0.36 seconds
GitLint PENDING 0.32 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 25.68 seconds
CheckAllWarning PASS 28.15 seconds
CheckSparse PASS 31.70 seconds
BuildKernel32 PASS 25.29 seconds
TestRunnerSetup PASS 478.26 seconds
TestRunner_l2cap-tester PASS 21.72 seconds
TestRunner_iso-tester PASS 35.78 seconds
TestRunner_bnep-tester PASS 4.90 seconds
TestRunner_mgmt-tester FAIL 126.75 seconds
TestRunner_rfcomm-tester PASS 8.05 seconds
TestRunner_sco-tester PASS 12.70 seconds
TestRunner_ioctl-tester PASS 8.47 seconds
TestRunner_mesh-tester PASS 6.17 seconds
TestRunner_smp-tester PASS 7.40 seconds
TestRunner_userchan-tester PASS 5.05 seconds
IncrementalBuild PENDING 0.95 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
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 - Set Flags 1 (Add to RL) Failed 0.151 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-04-22 3:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 1:21 [PATCH v2 0/2] Bluetooth: btmtksdio: ensure btmtksdio_close is executed before btmtksdio_remove Chris Lu
2025-04-22 1:21 ` [PATCH v2 1/2] Bluetooth: btmtksdio: Check function enabled before doing close Chris Lu
2025-04-22 3:07 ` bluez.test.bot [this message]
2025-04-22 1:21 ` [PATCH v2 2/2] Bluetooth: btmtksdio: Do close if SDIO card removed without close Chris Lu
2025-04-22 13:30 ` [PATCH v2 0/2] Bluetooth: btmtksdio: ensure btmtksdio_close is executed before btmtksdio_remove patchwork-bot+bluetooth
2025-05-21 15:23 ` patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2025-04-21 7:29 [PATCH v1 1/2] Bluetooth: btmtksdio: Check function enabled before doing close Chris Lu
2025-04-21 14:01 ` Bluetooth: btmtksdio: ensure btmtksdio_close is executed before btmtksdio_remove 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=68070806.170a0220.2dc04e.5251@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=chris.lu@mediatek.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