From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, oss@fourdim.xyz
Subject: RE: [v2] Bluetooth: L2CAP: Reject signalling responses in invalid states
Date: Tue, 29 Sep 2026 12:07:57 -0700 (PDT) [thread overview]
Message-ID: <6abc0c8d.0e70cbc3.28241.b92c@mx.google.com> (raw)
In-Reply-To: <20260929154219.2366060-1-oss@fourdim.xyz>
[-- Attachment #1: Type: text/plain, Size: 1308 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/1176242/
---Test result---
Test Summary:
CheckPatch PASS 0.54 seconds
VerifyFixes PASS 0.11 seconds
VerifySignedoff PASS 0.11 seconds
GitLint FAIL 0.28 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 21.64 seconds
CheckAllWarning PASS 25.20 seconds
CheckSparse PASS 26.48 seconds
BuildKernel32 PASS 23.03 seconds
CheckKernelLLVM PASS 21.04 seconds
TestRunnerSetup PASS 507.87 seconds
TestRunner_l2cap-tester PASS 23.22 seconds
IncrementalBuild PASS 19.97 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v2] Bluetooth: L2CAP: Reject signalling responses in invalid states
25: B3 Line contains hard tab characters (\t): " - resolve the patch conflict"
https://github.com/bluez/bluetooth-next/pull/842
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-09-29 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 15:42 [PATCH v2] Bluetooth: L2CAP: Reject signalling responses in invalid states Siwei Zhang
2026-09-29 19:07 ` 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=6abc0c8d.0e70cbc3.28241.b92c@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.