From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, m.szyprowski@samsung.com
Subject: RE: Bluetooth: btmrvl: fix event packet length validation
Date: Tue, 04 Aug 2026 05:16:25 -0700 (PDT) [thread overview]
Message-ID: <6a71d819.dbb26164.10167b.15c9@mx.google.com> (raw)
In-Reply-To: <20260804094632.87581-1-m.szyprowski@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 2025 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=1139978
---Test result---
Test Summary:
CheckPatch FAIL 0.53 seconds
VerifyFixes PASS 0.08 seconds
VerifySignedoff PASS 0.11 seconds
GitLint PASS 0.21 seconds
SubjectPrefix PASS 0.08 seconds
BuildKernel PASS 20.71 seconds
CheckAllWarning PASS 22.75 seconds
CheckSparse PASS 21.66 seconds
BuildKernel32 PASS 20.41 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 378.27 seconds
IncrementalBuild PASS 19.10 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: btmrvl: fix event packet length validation
ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 75e574f6a212 ("Bluetooth: btmrvl: validate event packet lengths")'
#80:
The event length validation added by 75e574f6a212 commit used a single
total: 1 errors, 0 warnings, 48 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/14729543.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: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
https://github.com/bluez/bluetooth-next/pull/531
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-08-04 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260804094640eucas1p1697cf118046108ce0d9d24127f68af12@eucas1p1.samsung.com>
2026-08-04 9:46 ` [PATCH] Bluetooth: btmrvl: fix event packet length validation Marek Szyprowski
2026-08-04 12:16 ` bluez.test.bot [this message]
2026-08-04 17:40 ` patchwork-bot+bluetooth
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=6a71d819.dbb26164.10167b.15c9@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=m.szyprowski@samsung.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