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: Bluetooth: L2CAP: ecred_reconfigure: send packed pdu, not stack pointer
Date: Mon, 11 May 2026 07:24:10 -0700 (PDT)	[thread overview]
Message-ID: <6a01e68a.050a0220.22ece4.8b51@mx.google.com> (raw)
In-Reply-To: <20260511122641.437434-1-michael.bommarito@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      0.59 seconds
GitLint                       PASS      0.23 seconds
SubjectPrefix                 PASS      0.08 seconds
BuildKernel                   PASS      25.17 seconds
CheckAllWarning               PASS      27.71 seconds
CheckSparse                   PASS      26.40 seconds
BuildKernel32                 PASS      24.56 seconds
TestRunnerSetup               PASS      525.11 seconds
TestRunner_l2cap-tester       PASS      378.39 seconds
IncrementalBuild              PASS      24.25 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: L2CAP: ecred_reconfigure: send packed pdu, not stack pointer
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#104: 
Commit 1c08108f3014 ("Bluetooth: L2CAP: Avoid -Wflex-array-member-not-at-end

total: 0 errors, 1 warnings, 0 checks, 8 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/14565486.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/165

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-05-11 14:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 12:26 [PATCH] Bluetooth: L2CAP: ecred_reconfigure: send packed pdu, not stack pointer Michael Bommarito
2026-05-11 14:24 ` bluez.test.bot [this message]
2026-05-11 16:30 ` patchwork-bot+bluetooth

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=6a01e68a.050a0220.22ece4.8b51@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