From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, bartosz.golaszewski@oss.qualcomm.com
Subject: RE: [RFC] power: sequencing: rename pwrseq_power_on/off() to pwrseq_vote_on/off()
Date: Fri, 07 Aug 2026 15:00:04 -0700 (PDT) [thread overview]
Message-ID: <6a765564.91d695f4.1c6cc1.fca2@mx.google.com> (raw)
In-Reply-To: <20260727-pwrseq-vote-rename-v1-1-a2029aeeac65@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 4286 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=1135051
---Test result---
Test Summary:
CheckPatch PASS 2.45 seconds
VerifyFixes PASS 0.11 seconds
VerifySignedoff PASS 0.10 seconds
GitLint PASS 0.25 seconds
SubjectPrefix FAIL 0.10 seconds
BuildKernel PASS 21.10 seconds
CheckAllWarning PASS 23.71 seconds
CheckSparse PASS 22.26 seconds
BuildKernel32 PASS 26.28 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup FAIL 360.15 seconds
TestRunner_l2cap-tester FAIL 0.10 seconds
TestRunner_iso-tester FAIL 0.10 seconds
TestRunner_bnep-tester FAIL 0.10 seconds
TestRunner_mgmt-tester FAIL 0.10 seconds
TestRunner_rfcomm-tester FAIL 0.10 seconds
TestRunner_sco-tester FAIL 0.10 seconds
TestRunner_ioctl-tester FAIL 0.10 seconds
TestRunner_mesh-tester FAIL 0.10 seconds
TestRunner_smp-tester FAIL 0.11 seconds
TestRunner_userchan-tester FAIL 0.10 seconds
TestRunner_6lowpan-tester FAIL 0.10 seconds
IncrementalBuild PASS 20.13 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
##############################
Test: TestRunnerSetup - FAIL
Desc: Setup kernel and bluez for test-runner
Output:
Kernel:
drivers/bluetooth/btnxpuart.c: In function ‘nxp_serdev_probe’:
drivers/bluetooth/btnxpuart.c:1875:9: error: implicit declaration of function ‘pwrseq_power_on’; did you mean ‘pwrseq_vote_on’? [-Werror=implicit-function-declaration]
1875 | err = pwrseq_power_on(pwrseq);
| ^~~~~~~~~~~~~~~
| pwrseq_vote_on
cc1: some warnings being treated as errors
make[4]: *** [scripts/Makefile.build:289: drivers/bluetooth/btnxpuart.o] Error 1
make[3]: *** [scripts/Makefile.build:549: drivers/bluetooth] Error 2
make[2]: *** [scripts/Makefile.build:549: drivers] Error 2
make[1]: *** [/github/workspace/src/src/Makefile:2187: .] Error 2
make: *** [Makefile:248: __sub-make] Error 2
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
No kernel image found
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
No kernel image found
##############################
Test: TestRunner_bnep-tester - FAIL
Desc: Run bnep-tester with test-runner
Output:
No kernel image found
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
No kernel image found
##############################
Test: TestRunner_rfcomm-tester - FAIL
Desc: Run rfcomm-tester with test-runner
Output:
No kernel image found
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
No kernel image found
##############################
Test: TestRunner_ioctl-tester - FAIL
Desc: Run ioctl-tester with test-runner
Output:
No kernel image found
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
No kernel image found
##############################
Test: TestRunner_smp-tester - FAIL
Desc: Run smp-tester with test-runner
Output:
No kernel image found
##############################
Test: TestRunner_userchan-tester - FAIL
Desc: Run userchan-tester with test-runner
Output:
No kernel image found
##############################
Test: TestRunner_6lowpan-tester - FAIL
Desc: Run 6lowpan-tester with test-runner
Output:
No kernel image found
https://github.com/bluez/bluetooth-next/pull/552
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-08-07 22:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 9:57 [PATCH RFC] power: sequencing: rename pwrseq_power_on/off() to pwrseq_vote_on/off() Bartosz Golaszewski
2026-07-27 10:10 ` sashiko-bot
2026-07-27 11:54 ` [RFC] " bluez.test.bot
2026-07-27 16:14 ` [PATCH RFC] " Bjorn Helgaas
2026-07-27 16:26 ` Chen-Yu Tsai
2026-07-30 16:52 ` Manivannan Sadhasivam
2026-07-27 20:28 ` Jeff Johnson
2026-08-07 22:00 ` bluez.test.bot [this message]
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=6a765564.91d695f4.1c6cc1.fca2@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=bartosz.golaszewski@oss.qualcomm.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.