All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, cochcoder@proton.me
Subject: RE: Bluetooth: L2CAP: Keep credits from completing security upgrades
Date: Thu, 15 Oct 2026 00:14:21 -0700 (PDT)	[thread overview]
Message-ID: <6ad07d4d.a438010f.f3b39.f7a9@mx.google.com> (raw)
In-Reply-To: <20261015052018.129971-1-cochcoder@proton.me>

[-- Attachment #1: Type: text/plain, Size: 1475 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/1186119/

---Test result---

Test Summary:
CheckPatch                    PASS      0.80 seconds
VerifyFixes                   PASS      0.06 seconds
VerifySignedoff               PASS      0.06 seconds
GitLint                       FAIL      0.19 seconds
SubjectPrefix                 PASS      0.90 seconds
BuildKernel                   PASS      29.55 seconds
CheckAllWarning               PASS      33.62 seconds
CheckSparse                   PASS      36.37 seconds
BuildKernel32                 PASS      29.44 seconds
CheckKernelLLVM               PASS      35.99 seconds
TestRunnerSetup               PASS      700.63 seconds
TestRunner_l2cap-tester       PASS      13.57 seconds
IncrementalBuild              PASS      27.97 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: L2CAP: Keep credits from completing security upgrades

38: B1 Line exceeds max length (82>80): "was split by the VM runner; corrected space-free filtered runs are reported above."
41: B1 Line exceeds max length (82>80): "failure) and combined 134/134; those are historical, not fresh full-suite results."


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

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-10-15  7:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  5:20 [PATCH] Bluetooth: L2CAP: Keep credits from completing security upgrades Kyle Pepper
2026-10-15  7: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=6ad07d4d.a438010f.f3b39.f7a9@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=cochcoder@proton.me \
    --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 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.