From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, tristmd@gmail.com
Subject: RE: [v3] Bluetooth: hci_bcm4377: validate firmware event length in completion ring
Date: Fri, 17 Apr 2026 05:08:24 -0700 (PDT) [thread overview]
Message-ID: <69e222b8.050a0220.1e8036.90ac@mx.google.com> (raw)
In-Reply-To: <20260417104639.2608008-1-tristmd@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 881 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=1082469
---Test result---
Test Summary:
CheckPatch PASS 0.74 seconds
GitLint PASS 0.34 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 27.35 seconds
CheckAllWarning PASS 29.94 seconds
CheckSparse PASS 29.01 seconds
BuildKernel32 PASS 26.57 seconds
TestRunnerSetup PASS 588.93 seconds
IncrementalBuild PASS 26.60 seconds
https://github.com/bluez/bluetooth-next/pull/99
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-04-17 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 10:46 [PATCH v3] Bluetooth: hci_bcm4377: validate firmware event length in completion ring Tristan Madani
2026-04-17 12:08 ` bluez.test.bot [this message]
2026-04-17 12:55 ` Neal Gompa
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=69e222b8.050a0220.1e8036.90ac@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=tristmd@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