Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, meatuni001@gmail.com
Subject: RE: Bluetooth: RFCOMM: add minimum length check in rfcomm_recv_frame
Date: Mon, 18 May 2026 23:15:33 -0700 (PDT)	[thread overview]
Message-ID: <6a0c0005.0aa2cc0a.15ad70.13c2@mx.google.com> (raw)
In-Reply-To: <20260519042017.29564-1-meatuni001@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1523 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=1097025

---Test result---

Test Summary:
CheckPatch                    PASS      0.50 seconds
GitLint                       FAIL      0.22 seconds
SubjectPrefix                 PASS      0.08 seconds
BuildKernel                   PASS      29.00 seconds
CheckAllWarning               PASS      28.96 seconds
CheckSparse                   PASS      27.22 seconds
BuildKernel32                 PASS      25.35 seconds
TestRunnerSetup               PASS      568.42 seconds
TestRunner_rfcomm-tester      PASS      63.54 seconds
IncrementalBuild              PASS      24.24 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: RFCOMM: add minimum length check in rfcomm_recv_frame

WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
11: B3 Line contains hard tab characters (\t): "	skb->len--; skb->tail--;"


https://github.com/bluez/bluetooth-next/pull/213

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-05-19  6:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19  4:20 [PATCH] Bluetooth: RFCOMM: add minimum length check in rfcomm_recv_frame Muhammad Bilal
2026-05-19  6:15 ` bluez.test.bot [this message]
2026-05-19  7:25 ` [PATCH v2] " Muhammad Bilal
2026-05-19 13:51 ` [PATCH] " Luiz Augusto von Dentz
2026-05-19 18:17 ` [PATCH v3] " Muhammad Bilal
2026-05-19 18:25   ` Luiz Augusto von Dentz
2026-05-19 18:48 ` [PATCH v4] " Muhammad Bilal
2026-05-19 19:50   ` [v4] " bluez.test.bot

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=6a0c0005.0aa2cc0a.15ad70.13c2@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