From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ceggers@arri.de
Subject: RE: doc/qualification: Updates for TCRL pkg101
Date: Mon, 02 Mar 2026 07:15:13 -0800 (PST) [thread overview]
Message-ID: <69a5a981.050a0220.275d4d.4f63@mx.google.com> (raw)
In-Reply-To: <20260302134540.25540-2-ceggers@arri.de>
[-- 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=1060034
---Test result---
Test Summary:
CheckPatch PENDING 0.46 seconds
GitLint PENDING 0.47 seconds
BuildEll PASS 20.79 seconds
BluezMake PASS 644.28 seconds
MakeCheck PASS 18.69 seconds
MakeDistcheck PASS 245.85 seconds
CheckValgrind PASS 296.92 seconds
CheckSmatch PASS 362.31 seconds
bluezmakeextell PASS 184.62 seconds
IncrementalBuild PENDING 0.54 seconds
ScanBuild PASS 1040.15 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-03-02 15:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 13:30 [PATCH BlueZ v2 00/15] doc/qualification: Updates for TCRL pkg101 Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 01/15] doc/qualification: gap-pics: add footnote for TSPC_GAP_21_9 feature Christian Eggers
2026-03-02 15:15 ` bluez.test.bot [this message]
2026-03-02 13:30 ` [PATCH BlueZ v2 02/15] doc/qualification: gap-pts: fix GAP/SEC/CSIGN/* tests Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 03/15] doc/qualification: gap-pts: fix GAP/SEC/SEM/BV-24-C test Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 04/15] doc/qualification: sm-pics: update capabilities in table 7b Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 05/15] doc/qualification: sm-pts: fix SM/PER/PKE/BI-03-C and BV-02-C tests Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 06/15] doc/qualification: sm-pts: fix SM/PER/SCPK/BI-03-C test Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 07/15] doc/qualification: sm-pts: add description for M/PER/PIS/BV-0[1-2]-C Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 08/15] doc/qualification: sm-pts: add description for SM/PER/KDU/BI-04-C test Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 09/15] doc/qualification: gatt-pts: add description for GATT/SR/GAW/BI-39-C Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 10/15] doc/qualification: gatt-pts: update description for GATT/SR/GAN/BV-01-C Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 11/15] doc/qualification: gatt-pts: add description for GATT/SR/GAN/BV-03-C Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 12/15] doc/qualification: gatt-pts: update description for GATT/SR/GAI/BV-01-C Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 13/15] doc/qualification: gatt-pts: add description for GATT/SR/GAI/BV-02-C Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 14/15] doc/qualification: l2cap-pts: remove redundant test documentation Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 15/15] doc/qualification: l2cap-pts: add descriptions for LE CFC tests Christian Eggers
2026-03-02 20:20 ` [PATCH BlueZ v2 00/15] doc/qualification: Updates for TCRL pkg101 patchwork-bot+bluetooth
2026-03-03 10:18 ` Christian Eggers
-- strict thread matches above, loose matches on Subject: below --
2026-02-27 15:53 [PATCH BlueZ 01/15] doc/qualification: gap-pics: add footnote for TSPC_GAP_21_9 feature Christian Eggers
2026-02-27 17:14 ` doc/qualification: Updates for TCRL pkg101 bluez.test.bot
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=69a5a981.050a0220.275d4d.4f63@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=ceggers@arri.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox