Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, 2022090917019@std.uestc.edu.cn
Subject: RE: Bluetooth: btintel: Fix insufficient skb length check in btintel_print_fseq_info()
Date: Thu, 14 May 2026 11:47:07 -0700 (PDT)	[thread overview]
Message-ID: <6a0618ab.8e75e0cb.1e3599.0d5c@mx.google.com> (raw)
In-Reply-To: <20260514164913.3123671-1-2022090917019@std.uestc.edu.cn>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.53 seconds
GitLint                       FAIL      0.23 seconds
SubjectPrefix                 PASS      0.07 seconds
BuildKernel                   PASS      24.46 seconds
CheckAllWarning               PASS      27.38 seconds
CheckSparse                   PASS      26.10 seconds
BuildKernel32                 PASS      24.20 seconds
TestRunnerSetup               PASS      539.18 seconds
IncrementalBuild              PASS      23.25 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: btintel: Fix insufficient skb length check in btintel_print_fseq_info()

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
1: T1 Title exceeds max length (82>80): "Bluetooth: btintel: Fix insufficient skb length check in btintel_print_fseq_info()"


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

---
Regards,
Linux Bluetooth


      parent reply	other threads:[~2026-05-14 18:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14 16:49 [PATCH] Bluetooth: btintel: Fix insufficient skb length check in btintel_print_fseq_info() Quan Sun
2026-05-14 17:35 ` Luiz Augusto von Dentz
2026-05-14 18:10   ` Quan Sun
2026-05-14 18:47 ` 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=6a0618ab.8e75e0cb.1e3599.0d5c@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=2022090917019@std.uestc.edu.cn \
    --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