From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1] monitor/l2cap: Add missing result for BT_L2CAP_PDU_ECRED_RECONF_RSP
Date: Wed, 04 Feb 2026 12:10:50 -0800 (PST) [thread overview]
Message-ID: <6983a7ca.050a0220.1cb2be.0534@mx.google.com> (raw)
In-Reply-To: <20260204185707.2327200-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1262 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=1050866
---Test result---
Test Summary:
CheckPatch PENDING 0.37 seconds
GitLint PENDING 0.41 seconds
BuildEll PASS 20.80 seconds
BluezMake PASS 648.70 seconds
MakeCheck PASS 19.04 seconds
MakeDistcheck PASS 247.83 seconds
CheckValgrind PASS 298.90 seconds
CheckSmatch PASS 359.17 seconds
bluezmakeextell PASS 189.42 seconds
IncrementalBuild PENDING 0.42 seconds
ScanBuild PASS 1039.75 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-02-04 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 18:57 [PATCH BlueZ v1] monitor/l2cap: Add missing result for BT_L2CAP_PDU_ECRED_RECONF_RSP Luiz Augusto von Dentz
2026-02-04 20:10 ` bluez.test.bot [this message]
2026-02-04 22:00 ` 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=6983a7ca.050a0220.1cb2be.0534@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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