From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: Add BASS unit tests for the SPE suite
Date: Wed, 04 Oct 2023 10:29:21 -0700 (PDT) [thread overview]
Message-ID: <651da0f1.920a0220.fdf08.028d@mx.google.com> (raw)
In-Reply-To: <20231004153150.3051-2-iulia.tanasescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 948 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=789981
---Test result---
Test Summary:
CheckPatch PASS 7.75 seconds
GitLint PASS 2.94 seconds
BuildEll PASS 29.11 seconds
BluezMake PASS 988.24 seconds
MakeCheck PASS 12.12 seconds
MakeDistcheck PASS 165.30 seconds
CheckValgrind PASS 264.72 seconds
CheckSmatch PASS 354.81 seconds
bluezmakeextell PASS 110.69 seconds
IncrementalBuild PASS 3537.44 seconds
ScanBuild PASS 1170.86 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-10-04 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 15:31 [PATCH BlueZ 0/4] Add BASS unit tests for the SPE suite Iulia Tanasescu
2023-10-04 15:31 ` [PATCH BlueZ 1/4] btio: Bind listener to bcaster addr based on dst opt Iulia Tanasescu
2023-10-04 17:29 ` bluez.test.bot [this message]
2023-10-04 15:31 ` [PATCH BlueZ 2/4] hciemu: Add support for setting emulator bdaddr Iulia Tanasescu
2023-10-04 15:31 ` [PATCH BlueZ 3/4] shared/bass: Add miscellaneous fixes Iulia Tanasescu
2023-10-04 15:31 ` [PATCH BlueZ 4/4] test-bass: Add unit tests for the SPE suite Iulia Tanasescu
2023-10-05 20:51 ` Luiz Augusto von Dentz
2023-10-10 15:45 ` Iulia Tanasescu
2023-10-05 21:00 ` [PATCH BlueZ 0/4] Add BASS " 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=651da0f1.920a0220.fdf08.028d@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.