From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: Update bcast ep register and config props
Date: Mon, 29 Jan 2024 08:52:44 -0800 (PST) [thread overview]
Message-ID: <65b7d7dc.170a0220.6c48d.3bc2@mx.google.com> (raw)
In-Reply-To: <20240129152928.3904-2-iulia.tanasescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 947 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=820948
---Test result---
Test Summary:
CheckPatch PASS 1.03 seconds
GitLint PASS 0.68 seconds
BuildEll PASS 24.02 seconds
BluezMake PASS 709.31 seconds
MakeCheck PASS 15.43 seconds
MakeDistcheck PASS 163.99 seconds
CheckValgrind PASS 226.10 seconds
CheckSmatch PASS 327.51 seconds
bluezmakeextell PASS 107.31 seconds
IncrementalBuild PASS 2007.50 seconds
ScanBuild PASS 944.40 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-01-29 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 15:29 [PATCH BlueZ 0/3] Update bcast ep register and config props Iulia Tanasescu
2024-01-29 15:29 ` [PATCH BlueZ 1/3] bap: Parse BIG handle at endpoint config Iulia Tanasescu
2024-01-29 16:52 ` bluez.test.bot [this message]
2024-01-29 15:29 ` [PATCH BlueZ 2/3] shared/bap: Set bcast stream metadata Iulia Tanasescu
2024-01-29 15:29 ` [PATCH BlueZ 3/3] client/player: Update bcast endpoint input prompts Iulia Tanasescu
2024-01-29 19:05 ` Luiz Augusto von Dentz
2024-01-29 19:11 ` Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2024-01-30 15:44 [PATCH BlueZ v2 1/4] bap: Parse BIG handle at endpoint config Iulia Tanasescu
2024-01-30 17:48 ` Update bcast ep register and config props 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=65b7d7dc.170a0220.6c48d.3bc2@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=iulia.tanasescu@nxp.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 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.