From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: Add local TMAS & GMAS servers
Date: Sat, 06 Dec 2025 04:02:40 -0800 (PST) [thread overview]
Message-ID: <69341b60.050a0220.316dd6.28a0@mx.google.com> (raw)
In-Reply-To: <c65bf870d8bc9813523302d28eb99b101673285d.1765018766.git.pav@iki.fi>
[-- 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=1031057
---Test result---
Test Summary:
CheckPatch PENDING 0.23 seconds
GitLint PENDING 0.30 seconds
BuildEll PASS 20.43 seconds
BluezMake PASS 650.07 seconds
MakeCheck PASS 22.24 seconds
MakeDistcheck PASS 242.90 seconds
CheckValgrind PASS 303.08 seconds
CheckSmatch PASS 354.72 seconds
bluezmakeextell PASS 185.31 seconds
IncrementalBuild PENDING 0.55 seconds
ScanBuild PASS 1029.81 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:[~2025-12-06 12:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 11:01 [PATCH BlueZ 00/11] Add local TMAS & GMAS servers Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 01/11] lib: move VCS, TMAS, GMAS uuid strings to uuid.h Pauli Virtanen
2025-12-06 12:02 ` bluez.test.bot [this message]
2025-12-06 11:01 ` [PATCH BlueZ 02/11] shared/tester: check size before trying debug print Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 03/11] shared/tmap, gmap: add macros for feature names and listing Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 04/11] bap: use tmap/gmap macros for listing features Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 05/11] shared/tmap: deactivate service if setting Role to 0 Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 06/11] shared/gmap: deactivate service or remove feature chrc if role removed Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 07/11] test-tmap: test removing and adding role Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 08/11] test-gmap: test removing, adding, and changing role Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 09/11] media: parse SupportedFeatures from registered MediaEndpoints Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 10/11] tmap: remove service on device remove Pauli Virtanen
2025-12-06 11:01 ` [PATCH BlueZ 11/11] gmap: " Pauli Virtanen
2025-12-08 19:20 ` [PATCH BlueZ 00/11] Add local TMAS & GMAS servers 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=69341b60.050a0220.316dd6.28a0@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