From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, frederic.danis@collabora.com
Subject: RE: [BlueZ,1/3] audio: Add ability to force CIS transport Links property
Date: Mon, 20 Apr 2026 10:44:53 -0700 (PDT) [thread overview]
Message-ID: <69e66615.c80a0220.2e6467.3285@mx.google.com> (raw)
In-Reply-To: <20260420161345.145089-1-frederic.danis@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 990 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=1083418
---Test result---
Test Summary:
CheckPatch PASS 1.69 seconds
GitLint PASS 1.04 seconds
BuildEll PASS 20.38 seconds
BluezMake PASS 641.43 seconds
MakeCheck PASS 18.94 seconds
MakeDistcheck PASS 248.34 seconds
CheckValgrind PASS 297.20 seconds
CheckSmatch PASS 348.73 seconds
bluezmakeextell PASS 184.69 seconds
IncrementalBuild PASS 642.44 seconds
ScanBuild PASS 1015.02 seconds
https://github.com/bluez/bluez/pull/2058
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-04-20 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 16:13 [PATCH BlueZ 1/3] audio: Add ability to force CIS transport Links property Frédéric Danis
2026-04-20 16:13 ` [PATCH BlueZ 2/3] doc: Add documentation for readwrite " Frédéric Danis
2026-04-20 16:13 ` [PATCH BlueZ 3/3] client/player: Add support to unlink transports Frédéric Danis
2026-04-20 16:32 ` [PATCH BlueZ 1/3] audio: Add ability to force CIS transport Links property Pauli Virtanen
2026-04-20 17:44 ` bluez.test.bot [this message]
2026-04-20 19:52 ` Luiz Augusto von Dentz
2026-04-21 8:22 ` Frédéric Danis
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=69e66615.c80a0220.2e6467.3285@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=frederic.danis@collabora.com \
--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