From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [v2,1/2] Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect
Date: Sun, 30 Aug 2026 06:00:50 -0700 (PDT) [thread overview]
Message-ID: <6a942982.35b683e3.3afc09.08da@mx.google.com> (raw)
In-Reply-To: <2b863abeea0ada6e990b07a7f3182e261ecd8e09.1788091154.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 1549 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=1153829
---Test result---
Test Summary:
CheckPatch PASS 1.96 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint FAIL 0.67 seconds
SubjectPrefix PASS 0.26 seconds
BuildKernel PASS 27.91 seconds
CheckAllWarning PASS 30.37 seconds
CheckSparse PASS 29.43 seconds
BuildKernel32 PASS 26.83 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 507.47 seconds
TestRunner_l2cap-tester PASS 64.99 seconds
IncrementalBuild PASS 29.26 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v2,1/2] Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect
28: B2 Line has trailing whitespace: " "
[v2,2/2] Bluetooth: L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM
18: B2 Line has trailing whitespace: " "
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
https://github.com/bluez/bluetooth-next/pull/667
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-08-30 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 12:04 [PATCH v2 1/2] Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect Pauli Virtanen
2026-08-30 12:04 ` [PATCH v2 2/2] Bluetooth: L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM Pauli Virtanen
2026-08-30 13:00 ` bluez.test.bot [this message]
2026-08-31 17:20 ` [PATCH v2 1/2] Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect 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=6a942982.35b683e3.3afc09.08da@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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