From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v3,BlueZ,1/8] lib: Add definitions for ISO socket
Date: Fri, 06 May 2022 17:41:43 -0700 (PDT) [thread overview]
Message-ID: <6275c047.1c69fb81.92fd0.f541@mx.google.com> (raw)
In-Reply-To: <20220506223139.3950573-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 998 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=639258
---Test result---
Test Summary:
CheckPatch PASS 4.35 seconds
GitLint PASS 2.96 seconds
Prep - Setup ELL PASS 41.52 seconds
Build - Prep PASS 0.69 seconds
Build - Configure PASS 8.13 seconds
Build - Make PASS 1206.06 seconds
Make Check PASS 11.90 seconds
Make Check w/Valgrind PASS 443.89 seconds
Make Distcheck PASS 232.72 seconds
Build w/ext ELL - Configure PASS 8.41 seconds
Build w/ext ELL - Make PASS 1272.91 seconds
Incremental Build with patchesPASS 3690.84 seconds
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2022-05-07 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 22:31 [PATCH v3 BlueZ 1/8] lib: Add definitions for ISO socket Luiz Augusto von Dentz
2022-05-06 22:31 ` [PATCH v3 BlueZ 2/8] shared/util: Decode BlueZ Experimental ISO Socket UUID Luiz Augusto von Dentz
2022-05-06 22:31 ` [PATCH v2 BlueZ 3/7] adapter: Add support for setting ISO Socket experimental feature Luiz Augusto von Dentz
2022-05-06 22:31 ` [PATCH v3 BlueZ 3/8] mgmt-tester: Fix Read Exp Feature tests Luiz Augusto von Dentz
2022-05-07 1:33 ` [v3,BlueZ,1/8] lib: Add definitions for ISO socket bluez.test.bot
2022-05-07 0:41 ` bluez.test.bot [this message]
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=6275c047.1c69fb81.92fd0.f541@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