From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, thomas.gerner@muenchen-mail.de
Subject: RE: Enable bluetooth on BeagleV-Ahead
Date: Sun, 11 Oct 2026 12:08:00 -0700 (PDT) [thread overview]
Message-ID: <6acbde90.116bf87f.27c28.9793@mx.google.com> (raw)
In-Reply-To: <578087018e274b0dcf25a523adc0d5cc590cceee.1791720467.git.thomas.gerner@muenchen-mail.de>
[-- Attachment #1: Type: text/plain, Size: 2791 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/series/1183346/
---Test result---
Test Summary:
CheckPatch FAIL 2.56 seconds
VerifyFixes PASS 0.25 seconds
VerifySignedoff PASS 0.26 seconds
GitLint FAIL 1.27 seconds
SubjectPrefix FAIL 0.13 seconds
BuildKernel PASS 29.13 seconds
CheckAllWarning PASS 33.25 seconds
CheckSparse PASS 35.80 seconds
BuildKernel32 PASS 29.21 seconds
CheckKernelLLVM PASS 32.92 seconds
TestRunnerSetup PASS 791.52 seconds
TestRunner_l2cap-tester PASS 12.72 seconds
TestRunner_iso-tester PASS 10.80 seconds
TestRunner_bnep-tester PASS 3.07 seconds
TestRunner_mgmt-tester PASS 61.09 seconds
TestRunner_rfcomm-tester PASS 4.50 seconds
TestRunner_sco-tester PASS 5.63 seconds
TestRunner_ioctl-tester PASS 4.63 seconds
TestRunner_mesh-tester PASS 5.46 seconds
TestRunner_smp-tester PASS 4.34 seconds
TestRunner_userchan-tester PASS 3.16 seconds
TestRunner_6lowpan-tester PASS 4.36 seconds
IncrementalBuild PASS 31.03 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[1/2] riscv: dts: thead: Enable bluetooth on BeagleV-Ahead
WARNING: please, no space before tabs
#226: FILE: arch/riscv/boot/dts/thead/th1520-beaglev-ahead.dts:401:
+^I^Ishutdown-gpios = <&gpio2 28 GPIO_ACTIVE_HIGH>; ^I/* BT-REG-ON */$
total: 0 errors, 1 warnings, 110 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14880416.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[1/2] riscv: dts: thead: Enable bluetooth on BeagleV-Ahead
6: B2 Line has trailing whitespace: "used as there is no driver. "
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
https://github.com/bluez/bluetooth-next/pull/896
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-11 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 13:37 [PATCH 0/2] Enable bluetooth on BeagleV-Ahead Thomas Gerner
2026-10-11 13:37 ` [PATCH 2/2] Bluetooth: btbcm: disable read tx power for BeagleV-Ahead Thomas Gerner
2026-10-11 19:08 ` bluez.test.bot [this message]
2026-10-11 13:37 ` [PATCH 1/2] riscv: dts: thead: Enable bluetooth on BeagleV-Ahead Thomas Gerner
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=6acbde90.116bf87f.27c28.9793@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=thomas.gerner@muenchen-mail.de \
/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