All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, oss@fourdim.xyz
Subject: RE: [v4,1/6] Bluetooth: L2CAP: Reject mode changes on connected channels
Date: Tue, 13 Oct 2026 13:18:02 -0700 (PDT)	[thread overview]
Message-ID: <6ace91fa.965be603.315991.fe97@mx.google.com> (raw)
In-Reply-To: <20261013153720.2635387-1-oss@fourdim.xyz>

[-- Attachment #1: Type: text/plain, Size: 1370 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/series/1184901/

---Test result---

Test Summary:
CheckPatch                    PASS      5.99 seconds
VerifyFixes                   PASS      0.11 seconds
VerifySignedoff               PASS      0.11 seconds
GitLint                       FAIL      3.59 seconds
SubjectPrefix                 PASS      0.74 seconds
BuildKernel                   PASS      30.53 seconds
CheckAllWarning               PASS      34.55 seconds
CheckSparse                   PASS      38.13 seconds
BuildKernel32                 PASS      28.88 seconds
CheckKernelLLVM               PASS      34.50 seconds
TestRunnerSetup               PASS      667.05 seconds
TestRunner_l2cap-tester       PASS      12.35 seconds
IncrementalBuild              PASS      47.78 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v4,5/6] Bluetooth: L2CAP: Only accept connection responses to outstanding requests

1: T1 Title exceeds max length (83>80): "[v4,5/6] Bluetooth: L2CAP: Only accept connection responses to outstanding requests"


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

---
Regards,
Linux Bluetooth


      parent reply	other threads:[~2026-10-13 20:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 15:36 [PATCH v4 1/6] Bluetooth: L2CAP: Reject mode changes on connected channels Siwei Zhang
2026-10-13 15:36 ` [PATCH v4 2/6] Bluetooth: L2CAP: Reject signalling responses in invalid states Siwei Zhang
2026-10-13 15:36 ` [PATCH v4 3/6] Bluetooth: L2CAP: Reject invalid TxWindow in configuration requests Siwei Zhang
2026-10-13 15:36 ` [PATCH v4 4/6] Bluetooth: L2CAP: Use default TxWindow for zero socket option Siwei Zhang
2026-10-13 15:36 ` [PATCH v4 5/6] Bluetooth: L2CAP: Only accept connection responses to outstanding requests Siwei Zhang
2026-10-13 15:36 ` [PATCH v4 6/6] Bluetooth: L2CAP: Remove dead configuration state code Siwei Zhang
2026-10-13 20:18 ` 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=6ace91fa.965be603.315991.fe97@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=oss@fourdim.xyz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.