From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, cochcoder@proton.me
Subject: RE: [RFC,v3,1/2] Bluetooth: L2CAP: Keep credits from completing security upgrades
Date: Thu, 15 Oct 2026 13:17:03 -0700 (PDT) [thread overview]
Message-ID: <6ad134bf.3c73b1f2.2d62aa.adbe@mx.google.com> (raw)
In-Reply-To: <20261015181624.48318-1-cochcoder@proton.me>
[-- Attachment #1: Type: text/plain, Size: 1073 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/1186712/
---Test result---
Test Summary:
CheckPatch PASS 1.74 seconds
VerifyFixes PASS 0.12 seconds
VerifySignedoff PASS 0.12 seconds
GitLint PASS 0.64 seconds
SubjectPrefix PASS 0.23 seconds
BuildKernel PASS 31.51 seconds
CheckAllWarning PASS 33.73 seconds
CheckSparse PASS 36.47 seconds
BuildKernel32 PASS 29.38 seconds
CheckKernelLLVM PASS 35.28 seconds
TestRunnerSetup PASS 702.28 seconds
TestRunner_l2cap-tester PASS 12.79 seconds
IncrementalBuild PASS 31.19 seconds
https://github.com/bluez/bluetooth-next/pull/952
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-10-15 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 3:19 [RFC PATCH] Bluetooth: L2CAP: tolerate zero-ident LE credit indications Kyle Pepper
2026-10-13 4:20 ` [RFC] " bluez.test.bot
2026-10-13 14:43 ` [RFC PATCH] " Luiz Augusto von Dentz
2026-10-15 18:31 ` cochcoder
2026-10-15 5:28 ` [RFC PATCH v2] " Kyle Pepper
2026-10-15 6:42 ` [RFC,v2] " bluez.test.bot
2026-10-15 18:16 ` [RFC PATCH v3 1/2] Bluetooth: L2CAP: Keep credits from completing security upgrades Kyle Pepper
2026-10-15 18:17 ` [RFC PATCH v3 2/2] Bluetooth: L2CAP: tolerate zero-ident LE credit indications Kyle Pepper
2026-10-15 20:17 ` 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=6ad134bf.3c73b1f2.2d62aa.adbe@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.