From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: RE: HID: Hardening report validation and unnumbered report handling
Date: Wed, 14 Oct 2026 17:11:14 -0700 (PDT) [thread overview]
Message-ID: <6ad01a22.bd274c6e.190902.f3a5@mx.google.com> (raw)
In-Reply-To: <20261012-hid-core-report-validation-v1-1-e0dd5cb60b2e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2151 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/1184349/
---Test result---
Test Summary:
CheckPatch PASS 4.79 seconds
VerifyFixes PASS 0.08 seconds
VerifySignedoff PASS 0.08 seconds
GitLint PASS 1.94 seconds
SubjectPrefix FAIL 0.81 seconds
BuildKernel PASS 22.01 seconds
CheckAllWarning PASS 25.11 seconds
CheckSparse PASS 27.51 seconds
BuildKernel32 PASS 21.84 seconds
CheckKernelLLVM PASS 24.35 seconds
TestRunnerSetup PASS 516.26 seconds
TestRunner_l2cap-tester PASS 13.81 seconds
TestRunner_iso-tester PASS 11.62 seconds
TestRunner_bnep-tester PASS 2.81 seconds
TestRunner_mgmt-tester PASS 83.12 seconds
TestRunner_rfcomm-tester PASS 4.13 seconds
TestRunner_sco-tester PASS 5.04 seconds
TestRunner_ioctl-tester PASS 4.13 seconds
TestRunner_mesh-tester PASS 5.11 seconds
TestRunner_smp-tester PASS 4.01 seconds
TestRunner_userchan-tester PASS 2.86 seconds
TestRunner_6lowpan-tester PASS 4.01 seconds
IncrementalBuild PASS 31.37 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
https://github.com/bluez/bluetooth-next/pull/938
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-15 0:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 3:42 [PATCH 0/9] HID: Hardening report validation and unnumbered report handling Dmitry Torokhov
2026-10-13 3:42 ` [PATCH 1/9] Bluetooth: HIDP: Fix GET_REPORT and SET_REPORT for unnumbered reports Dmitry Torokhov
2026-10-13 3:56 ` HID: Hardening report validation and unnumbered report handling bluez.test.bot
2026-10-15 0:11 ` bluez.test.bot [this message]
2026-10-13 3:42 ` [PATCH 2/9] HID: core: Fix GET_REPORT input processing for unnumbered reports Dmitry Torokhov
2026-10-13 3:42 ` [PATCH 3/9] HID: core: Reject mixing numbered and " Dmitry Torokhov
2026-10-13 3:42 ` [PATCH 4/9] HID: core: Validate GET_REPORT report ID centrally Dmitry Torokhov
2026-10-13 3:42 ` [PATCH 5/9] HID: i2c-hid: Drop redundant report ID validation Dmitry Torokhov
2026-10-13 3:42 ` [PATCH 6/9] HID: goodix-spi: " Dmitry Torokhov
2026-10-13 3:42 ` [PATCH 7/9] HID: intel-thc-hid: Drop redundant report ID validation in quicki2c Dmitry Torokhov
2026-10-13 3:42 ` [PATCH 8/9] HID: multitouch: Drop redundant report ID validation in mt_get_feature Dmitry Torokhov
2026-10-13 3:42 ` [PATCH 9/9] HID: playstation: Drop redundant report ID validation in ps_get_report Dmitry Torokhov
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=6ad01a22.bd274c6e.190902.f3a5@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=dmitry.torokhov@gmail.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