From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, acharyalaxman8848@gmail.com
Subject: RE: Bluetooth: btintel: harden version TLV parsing
Date: Mon, 31 Aug 2026 05:29:04 -0700 (PDT) [thread overview]
Message-ID: <6a957390.0c0d0188.1899c7.27c6@mx.google.com> (raw)
In-Reply-To: <20260831095923.18830-2-acharyalaxman8848@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1181 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=1154381
---Test result---
Test Summary:
CheckPatch PASS 1.57 seconds
VerifyFixes PASS 0.11 seconds
VerifySignedoff PASS 0.10 seconds
GitLint PASS 0.75 seconds
SubjectPrefix PASS 0.30 seconds
BuildKernel PASS 18.50 seconds
CheckAllWarning PASS 21.85 seconds
CheckSparse PASS 20.30 seconds
BuildKernel32 PASS 18.52 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 314.40 seconds
IncrementalBuild PASS 22.21 seconds
Details
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
https://github.com/bluez/bluetooth-next/pull/673
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-08-31 12:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 17:15 [PATCH v2 0/3] Bluetooth: btintel: harden version TLV parsing Laxman Acharya Padhya
2026-08-14 17:15 ` [PATCH v2 1/3] Bluetooth: btintel: validate version TLV value lengths Laxman Acharya Padhya
2026-08-14 18:29 ` Bluetooth: btintel: harden version TLV parsing bluez.test.bot
2026-08-14 17:15 ` [PATCH v2 2/3] Bluetooth: btintel: bound firmware ID by TLV length Laxman Acharya Padhya
2026-08-14 17:15 ` [PATCH v2 3/3] Bluetooth: btintel: propagate version TLV parsing errors Laxman Acharya Padhya
2026-08-14 18:46 ` Ali Ahmet Memis
2026-08-31 9:59 ` [PATCH v3 0/3] Bluetooth: btintel: harden version TLV parsing Laxman Acharya Padhya
2026-08-31 9:59 ` [PATCH v3 1/3] Bluetooth: btintel: validate version TLV value lengths Laxman Acharya Padhya
2026-08-31 11:05 ` K, Kiran
2026-08-31 12:29 ` bluez.test.bot [this message]
2026-08-31 9:59 ` [PATCH v3 2/3] Bluetooth: btintel: bound firmware ID by TLV length Laxman Acharya Padhya
2026-08-31 11:05 ` K, Kiran
2026-08-31 9:59 ` [PATCH v3 3/3] Bluetooth: btintel: propagate version TLV parsing errors Laxman Acharya Padhya
2026-08-31 11:05 ` K, Kiran
2026-08-31 17:20 ` [PATCH v3 0/3] Bluetooth: btintel: harden version TLV parsing 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=6a957390.0c0d0188.1899c7.27c6@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=acharyalaxman8848@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