From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, meatuni001@gmail.com
Subject: RE: [v2] Bluetooth: HIDP: fix missing length checks in hidp_input_report()
Date: Wed, 20 May 2026 17:16:47 -0700 (PDT) [thread overview]
Message-ID: <6a0e4eef.3ee1b803.2b2d14.6a46@mx.google.com> (raw)
In-Reply-To: <20260520214133.27746-1-meatuni001@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2191 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=1098310
---Test result---
Test Summary:
CheckPatch FAIL 0.65 seconds
GitLint PASS 0.27 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 25.15 seconds
CheckAllWarning PASS 28.02 seconds
CheckSparse PASS 27.24 seconds
BuildKernel32 PASS 26.55 seconds
TestRunnerSetup PASS 541.52 seconds
TestRunner_l2cap-tester PASS 378.34 seconds
TestRunner_iso-tester PASS 597.47 seconds
TestRunner_bnep-tester PASS 18.47 seconds
TestRunner_mgmt-tester PASS 2023.12 seconds
TestRunner_rfcomm-tester PASS 63.46 seconds
TestRunner_sco-tester PASS 141.48 seconds
TestRunner_ioctl-tester PASS 133.21 seconds
TestRunner_mesh-tester PASS 59.62 seconds
TestRunner_smp-tester PASS 17.73 seconds
TestRunner_userchan-tester PASS 19.12 seconds
TestRunner_6lowpan-tester PASS 51.01 seconds
IncrementalBuild PASS 26.59 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2] Bluetooth: HIDP: fix missing length checks in hidp_input_report()
WARNING: The commit message has 'stable@', perhaps it also needs a 'Fixes:' tag?
total: 0 errors, 1 warnings, 0 checks, 34 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.
/github/workspace/src/patch/14585274.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.
https://github.com/bluez/bluetooth-next/pull/223
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-05-21 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 23:48 [PATCH] Bluetooth: HIDP: fix missing length checks in hidp_input_report() Muhammad Bilal
2026-05-18 2:56 ` bluez.test.bot
2026-05-18 5:18 ` [PATCH] " Greg KH
2026-05-20 21:41 ` [PATCH v2] " Muhammad Bilal
2026-05-20 22:03 ` Luiz Augusto von Dentz
2026-05-20 22:56 ` [PATCH v3] " Muhammad Bilal
2026-05-21 1:24 ` [v3] " bluez.test.bot
2026-05-21 0:16 ` 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=6a0e4eef.3ee1b803.2b2d14.6a46@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=meatuni001@gmail.com \
/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