From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, rdunlap@infradead.org
Subject: RE: docs: ioctl-number: update entries
Date: Sat, 14 Nov 2026 16:43:27 -0800 (PST) [thread overview]
Message-ID: <6af9002f.fc76328d.377715.22c5@mx.google.com> (raw)
In-Reply-To: <20261114202653.3113381-2-rdunlap@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 2364 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/1211568/
---Test result---
Test Summary:
CheckPatch PASS 6.47 seconds
VerifyFixes PASS 0.09 seconds
VerifySignedoff PASS 0.09 seconds
GitLint PASS 3.15 seconds
SubjectPrefix FAIL 1.04 seconds
BuildKernel PASS 28.24 seconds
CheckAllWarning PASS 32.10 seconds
CheckSparse PASS 34.64 seconds
BuildKernel32 PASS 28.08 seconds
CheckKernelLLVM PASS 28.06 seconds
TestRunnerSetup PASS 661.82 seconds
TestRunner_l2cap-tester PASS 15.75 seconds
TestRunner_iso-tester PASS 12.64 seconds
TestRunner_bnep-tester PASS 3.08 seconds
TestRunner_mgmt-tester PASS 86.15 seconds
TestRunner_rfcomm-tester PASS 4.35 seconds
TestRunner_sco-tester PASS 5.45 seconds
TestRunner_ioctl-tester PASS 4.50 seconds
TestRunner_mesh-tester PASS 5.37 seconds
TestRunner_smp-tester PASS 4.23 seconds
TestRunner_userchan-tester PASS 3.12 seconds
TestRunner_6lowpan-tester PASS 4.34 seconds
IncrementalBuild PASS 36.52 seconds
Details
##############################
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
https://github.com/bluez/bluetooth-next/pull/1136
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-15 0:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 20:26 [PATCH 00/12] docs: ioctl-number: update entries Randy Dunlap
2026-11-14 20:26 ` [PATCH 01/12] docs: ioctl-number: update MM entries Randy Dunlap
2026-11-15 0:43 ` bluez.test.bot [this message]
2026-11-14 20:26 ` [PATCH 02/12] docs: ioctl-number: update sound entries Randy Dunlap
2026-11-14 20:26 ` [PATCH 03/12] docs: ioctl-number: update block entries Randy Dunlap
2026-11-14 20:26 ` [PATCH 04/12] docs: ioctl-number: update networking entries Randy Dunlap
2026-11-14 20:26 ` [PATCH 05/12] docs: ioctl-number: update video/fbdev entries Randy Dunlap
2026-11-14 20:26 ` [PATCH 06/12] docs: ioctl-number: update SCSI entries Randy Dunlap
2026-11-14 20:26 ` [PATCH 07/12] docs: ioctl-number: update MTD entries Randy Dunlap
2026-11-14 20:26 ` [PATCH 08/12] docs: ioctl-number: update USB entries Randy Dunlap
2026-11-14 20:26 ` [PATCH 09/12] docs: ioctl-number: update virtualization entries Randy Dunlap
2026-11-14 20:26 ` [PATCH 10/12] docs: ioctl-number: update FS entries Randy Dunlap
2026-11-14 20:26 ` [PATCH 11/12] docs: ioctl-number: update platform entries Randy Dunlap
2026-11-14 20:26 ` [PATCH 12/12] docs: ioctl-number: update DRM entries Randy Dunlap
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=6af9002f.fc76328d.377715.22c5@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=rdunlap@infradead.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