From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, alexis.lothore@bootlin.com
Subject: RE: bluetooth: hci_wilc: add new bluetooth driver
Date: Wed, 12 Feb 2025 08:36:46 -0800 (PST) [thread overview]
Message-ID: <67acce1e.050a0220.3f628.b64a@mx.google.com> (raw)
In-Reply-To: <20250212-wilc3000_bt-v1-1-9609b784874e@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 3098 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=933239
---Test result---
Test Summary:
CheckPatch PENDING 0.23 seconds
GitLint PENDING 0.20 seconds
SubjectPrefix FAIL 1.93 seconds
BuildKernel PASS 25.72 seconds
CheckAllWarning PASS 28.21 seconds
CheckSparse PASS 32.61 seconds
BuildKernel32 PASS 25.49 seconds
TestRunnerSetup PASS 450.87 seconds
TestRunner_l2cap-tester PASS 21.43 seconds
TestRunner_iso-tester FAIL 65.35 seconds
TestRunner_bnep-tester PASS 5.04 seconds
TestRunner_mgmt-tester FAIL 123.64 seconds
TestRunner_rfcomm-tester PASS 7.87 seconds
TestRunner_sco-tester PASS 9.78 seconds
TestRunner_ioctl-tester PASS 8.67 seconds
TestRunner_mesh-tester PASS 6.31 seconds
TestRunner_smp-tester PASS 10.92 seconds
TestRunner_userchan-tester PASS 5.35 seconds
IncrementalBuild PENDING 0.60 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
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
BUG: KASAN: slab-use-after-free in iso_conn_hold_unless_zero+0x78/0x1c0
Total: 125, Passed: 121 (96.8%), Failed: 0, Not Run: 4
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 490, Passed: 483 (98.6%), Failed: 3, Not Run: 4
Failed Test Cases
LL Privacy - Add Device 3 (AL is full) Failed 0.186 seconds
LL Privacy - Set Flags 1 (Add to RL) Failed 0.138 seconds
LL Privacy - Set Flags 3 (2 Devices to RL) Failed 0.174 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-02-12 16:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 15:46 [PATCH 00/12] bluetooth: hci_wilc: add new bluetooth driver Alexis Lothoré
2025-02-12 15:46 ` [PATCH 01/12] dt-bindings: bluetooth: describe wilc 3000 bluetooth chip Alexis Lothoré
2025-02-12 16:36 ` bluez.test.bot [this message]
2025-02-13 9:25 ` Krzysztof Kozlowski
2025-02-13 9:25 ` Krzysztof Kozlowski
2025-02-13 15:25 ` Alexis Lothoré
2025-02-13 15:25 ` Alexis Lothoré
2025-02-14 7:47 ` Krzysztof Kozlowski
2025-02-14 7:47 ` Krzysztof Kozlowski
2025-02-12 15:46 ` [PATCH 02/12] wifi: wilc1000: add a read-modify-write API for registers accesses Alexis Lothoré
2025-02-12 15:46 ` [PATCH 03/12] wifi: wilc1000: add lock to prevent concurrent firmware startup Alexis Lothoré
2025-02-12 15:46 ` [PATCH 04/12] wifi: wilc1000: allow to use acquire/release bus in other parts of driver Alexis Lothoré
2025-02-12 15:46 ` [PATCH 05/12] wifi: wilc1000: do not depend on power save flag to wake up chip Alexis Lothoré
2025-02-12 15:46 ` [PATCH 06/12] wifi: wilc1000: remove timeout parameter from set_power_mgmt Alexis Lothoré
2025-02-12 15:46 ` [PATCH 07/12] wifi: wilc1000: reorganize makefile objs into sorted list Alexis Lothoré
2025-02-12 15:46 ` [PATCH 08/12] wifi: wilc1000: add basic functions to allow bluetooth bringup Alexis Lothoré
2025-02-12 15:46 ` [PATCH 09/12] wifi: wilc1000: disable firmware power save if bluetooth is in use Alexis Lothoré
2025-02-16 16:07 ` Simon Horman
2025-02-16 16:07 ` Simon Horman
2025-02-12 15:46 ` [PATCH 10/12] bluetooth: hci_wilc: add wilc hci driver Alexis Lothoré
2025-02-12 16:14 ` Luiz Augusto von Dentz
2025-02-12 16:14 ` Luiz Augusto von Dentz
2025-02-12 17:01 ` Alexis Lothoré
2025-02-12 17:01 ` Alexis Lothoré
2025-02-13 9:24 ` Krzysztof Kozlowski
2025-02-13 9:24 ` Krzysztof Kozlowski
2025-02-13 15:30 ` Alexis Lothoré
2025-02-13 15:30 ` Alexis Lothoré
2025-02-12 15:46 ` [PATCH 11/12] ARM: dts: at91-sama5d27_wlsom1: update bluetooth chip description Alexis Lothoré
2025-02-12 15:46 ` [PATCH 12/12] MAINTAINERS: add entry for new wilc3000 bluetooth driver Alexis Lothoré
2025-02-12 22:08 ` [PATCH 00/12] bluetooth: hci_wilc: add new " Rob Herring (Arm)
2025-02-12 22:08 ` Rob Herring (Arm)
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=67acce1e.050a0220.3f628.b64a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=alexis.lothore@bootlin.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 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.