From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, xmei5@asu.edu
Subject: RE: Bluetooth: qca: fix NVM tag length underflow in TLV parser
Date: Sat, 04 Jul 2026 17:04:29 -0700 (PDT) [thread overview]
Message-ID: <6a499f8d.36695ec4.2a7238.abf1@mx.google.com> (raw)
In-Reply-To: <20260704231030.996390-1-xmei5@asu.edu>
[-- Attachment #1: Type: text/plain, Size: 2543 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=1121634
---Test result---
Test Summary:
CheckPatch FAIL 0.72 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint FAIL 0.32 seconds
SubjectPrefix PASS 0.12 seconds
BuildKernel PASS 27.03 seconds
CheckAllWarning PASS 30.07 seconds
CheckSparse PASS 28.11 seconds
BuildKernel32 PASS 26.15 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 496.12 seconds
IncrementalBuild PASS 30.35 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: qca: fix NVM tag length underflow in TLV parser
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#108:
vmalloc'd firmware buffer (and the EDL_TAG_ID_* handlers can write past it).
WARNING: Reported-by: should be immediately followed by Closes: with a URL to the report
#133:
Reported-by: Weiming Shi <bestswngs@gmail.com>
Assisted-by: Claude:claude-opus-4-8
total: 0 errors, 2 warnings, 8 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/14664142.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:
Bluetooth: qca: fix NVM tag length underflow in TLV parser
15: B1 Line exceeds max length (99>80): " BUG: KASAN: vmalloc-out-of-bounds in qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421)"
21: B1 Line exceeds max length (93>80): " qca_download_firmware.isra.0 (drivers/bluetooth/btqca.c:421 drivers/bluetooth/btqca.c:617)"
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
https://github.com/bluez/bluetooth-next/pull/396
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-07-05 0:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 23:10 [PATCH bluetooth] Bluetooth: qca: fix NVM tag length underflow in TLV parser Xiang Mei
2026-07-05 0:04 ` bluez.test.bot [this message]
2026-07-05 9:41 ` Johan Hovold
2026-07-07 17:55 ` Xiang Mei
2026-07-08 14:21 ` Johan Hovold
2026-07-08 15:15 ` Luiz Augusto von Dentz
2026-07-09 11:06 ` Johan Hovold
2026-07-06 9:39 ` Bartosz Golaszewski
2026-07-07 17:30 ` 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=6a499f8d.36695ec4.2a7238.abf1@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=xmei5@asu.edu \
/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