Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, michael.bommarito@gmail.com
Subject: RE: [v4] Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig
Date: Thu, 21 May 2026 12:08:01 -0700 (PDT)	[thread overview]
Message-ID: <6a0f5811.362730bf.1fba55.2b77@mx.google.com> (raw)
In-Reply-To: <20260521144518.1361335-1-michael.bommarito@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.00 seconds
VerifyFixes                   PASS      0.14 seconds
VerifySignedoff               PASS      0.14 seconds
GitLint                       PASS      0.35 seconds
SubjectPrefix                 PASS      0.13 seconds
BuildKernel                   PASS      27.44 seconds
CheckAllWarning               PASS      29.96 seconds
CheckSparse                   PASS      28.91 seconds
BuildKernel32                 PASS      28.26 seconds
TestRunnerSetup               PASS      587.14 seconds
TestRunner_l2cap-tester       PASS      59.17 seconds
IncrementalBuild              PASS      25.06 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v4] Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig
WARNING: The commit message has 'stable@', perhaps it also needs a 'Fixes:' tag?

total: 0 errors, 1 warnings, 0 checks, 65 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

/github/workspace/src/patch/14587556.patch has style problems, please review.

NOTE: Ignored message types: UNKNOWN_COMMIT_ID

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.




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

---
Regards,
Linux Bluetooth


      parent reply	other threads:[~2026-05-21 19:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20 13:50 [PATCH v2] Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig Michael Bommarito
2026-05-20 14:00 ` Luiz Augusto von Dentz
2026-05-20 14:12   ` Michael Bommarito
2026-05-20 15:18     ` Luiz Augusto von Dentz
2026-05-20 15:23       ` Michael Bommarito
2026-05-20 16:15         ` Luiz Augusto von Dentz
2026-05-20 14:48 ` [v2] " bluez.test.bot
2026-05-21  0:05 ` [PATCH v3] " Michael Bommarito
2026-05-21 12:51   ` Luiz Augusto von Dentz
2026-05-21 14:45   ` [PATCH v4] " Michael Bommarito
2026-05-21 17:23     ` [v4] " bluez.test.bot
2026-05-21 19:08     ` 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=6a0f5811.362730bf.1fba55.2b77@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=michael.bommarito@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