From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, catalin.popescu@leica-geosystems.com
Subject: RE: [next,v4,1/2] dt-bindings: net: bluetooth: nxp: add support for supply and reset
Date: Wed, 02 Jul 2025 05:38:49 -0700 (PDT) [thread overview]
Message-ID: <68652859.050a0220.250d4b.df47@mx.google.com> (raw)
In-Reply-To: <20250702114105.2229008-1-catalin.popescu@leica-geosystems.com>
[-- Attachment #1: Type: text/plain, Size: 3786 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=978194
---Test result---
Test Summary:
CheckPatch PENDING 0.23 seconds
GitLint PENDING 0.19 seconds
SubjectPrefix FAIL 0.39 seconds
BuildKernel PASS 24.30 seconds
CheckAllWarning PASS 26.98 seconds
CheckSparse PASS 30.01 seconds
BuildKernel32 PASS 24.08 seconds
TestRunnerSetup FAIL 100.13 seconds
TestRunner_l2cap-tester FAIL 0.10 seconds
TestRunner_iso-tester FAIL 0.10 seconds
TestRunner_bnep-tester FAIL 0.09 seconds
TestRunner_mgmt-tester FAIL 0.10 seconds
TestRunner_rfcomm-tester FAIL 0.17 seconds
TestRunner_sco-tester FAIL 0.10 seconds
TestRunner_ioctl-tester FAIL 0.09 seconds
TestRunner_mesh-tester FAIL 0.10 seconds
TestRunner_smp-tester FAIL 0.09 seconds
TestRunner_userchan-tester FAIL 0.10 seconds
IncrementalBuild PENDING 0.91 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: TestRunnerSetup - FAIL
Desc: Setup kernel and bluez for test-runner
Output:
Bluez:
src/device.c: In function ‘connect_profiles’:
src/device.c:2689:6: error: ‘ERR_BREDR_CONN_PROFILE_UNAVAILABLE’ undeclared (first use in this function)
2689 | ERR_BREDR_CONN_PROFILE_UNAVAILABLE);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/device.c:2689:6: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [Makefile:11162: src/bluetoothd-device.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:4690: all] Error 2
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
No tester found
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
No tester found
##############################
Test: TestRunner_bnep-tester - FAIL
Desc: Run bnep-tester with test-runner
Output:
No tester found
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
No tester found
##############################
Test: TestRunner_rfcomm-tester - FAIL
Desc: Run rfcomm-tester with test-runner
Output:
No tester found
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
No tester found
##############################
Test: TestRunner_ioctl-tester - FAIL
Desc: Run ioctl-tester with test-runner
Output:
No tester found
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
No tester found
##############################
Test: TestRunner_smp-tester - FAIL
Desc: Run smp-tester with test-runner
Output:
No tester found
##############################
Test: TestRunner_userchan-tester - FAIL
Desc: Run userchan-tester with test-runner
Output:
No tester found
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-07-02 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 11:41 [PATCH next v4 1/2] dt-bindings: net: bluetooth: nxp: add support for supply and reset Catalin Popescu
2025-07-02 11:41 ` [PATCH next v4 2/2] Bluetooth: btnxpuart: implement powerup sequence Catalin Popescu
2025-07-02 12:38 ` bluez.test.bot [this message]
2025-07-10 13:40 ` [PATCH next v4 1/2] dt-bindings: net: bluetooth: nxp: add support for supply and reset patchwork-bot+bluetooth
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=68652859.050a0220.250d4b.df47@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=catalin.popescu@leica-geosystems.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