From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, meatuni001@gmail.com
Subject: RE: [v2] Bluetooth: RFCOMM: add minimum length check in rfcomm_recv_frame
Date: Tue, 19 May 2026 02:14:21 -0700 (PDT) [thread overview]
Message-ID: <6a0c29ed.9652e1b4.14d1d9.40b9@mx.google.com> (raw)
In-Reply-To: <20260519073003.34206-1-meatuni001@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 936 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=1097117
---Test result---
Test Summary:
CheckPatch PASS 0.42 seconds
GitLint PASS 0.18 seconds
SubjectPrefix PASS 0.06 seconds
BuildKernel PASS 21.39 seconds
CheckAllWarning PASS 23.49 seconds
CheckSparse PASS 21.19 seconds
BuildKernel32 PASS 20.51 seconds
TestRunnerSetup PASS 420.35 seconds
TestRunner_rfcomm-tester PASS 59.01 seconds
IncrementalBuild PASS 19.56 seconds
https://github.com/bluez/bluetooth-next/pull/214
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-05-19 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 7:30 [PATCH v2] Bluetooth: RFCOMM: add minimum length check in rfcomm_recv_frame Muhammad Bilal
2026-05-19 9:14 ` 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=6a0c29ed.9652e1b4.14d1d9.40b9@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