From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, silviu.barbulescu@nxp.com
Subject: RE: Add support for multiple BISes
Date: Thu, 26 Oct 2023 10:45:33 -0700 (PDT) [thread overview]
Message-ID: <653aa5bd.050a0220.81f15.2562@mx.google.com> (raw)
In-Reply-To: <20231026145047.4637-2-silviu.barbulescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 949 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=796846
---Test result---
Test Summary:
CheckPatch PASS 3.65 seconds
GitLint PASS 1.79 seconds
BuildEll PASS 33.84 seconds
BluezMake PASS 1085.99 seconds
MakeCheck PASS 13.29 seconds
MakeDistcheck PASS 215.11 seconds
CheckValgrind PASS 325.67 seconds
CheckSmatch PASS 449.76 seconds
bluezmakeextell PASS 143.73 seconds
IncrementalBuild PASS 5540.16 seconds
ScanBuild PASS 1243.12 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-10-26 17:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 14:50 [PATCH 0/6] Add support for multiple BISes Silviu Florian Barbulescu
2023-10-26 14:50 ` [PATCH 1/6] bap: Fix source+sink endpoint registration Silviu Florian Barbulescu
2023-10-26 17:45 ` bluez.test.bot [this message]
2023-10-26 14:50 ` [PATCH 2/6] " Silviu Florian Barbulescu
2023-10-26 14:50 ` [PATCH 3/6] src: Add support for the number of BISes in the main.conf Silviu Florian Barbulescu
2023-10-26 14:50 ` [PATCH 4/6] Add support for multiple BISes Silviu Florian Barbulescu
2023-10-26 14:50 ` [PATCH 5/6] profiles/audio/transport.c: " Silviu Florian Barbulescu
2023-10-26 14:50 ` [PATCH 6/6] client/player.c: " Silviu Florian Barbulescu
2023-10-26 21:32 ` [PATCH 0/6] " Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2024-01-04 17:16 [PATCH 1/2] client/player.c: " Silviu Florian Barbulescu
2024-01-04 17:36 ` bluez.test.bot
2024-01-05 14:33 [PATCH v2 1/2] client/player.c: " Silviu Florian Barbulescu
2024-01-05 16:19 ` bluez.test.bot
2024-01-08 16:42 [PATCH v3 1/3] client/player.c: " Silviu Florian Barbulescu
2024-01-08 18:29 ` bluez.test.bot
2024-01-10 16:10 [PATCH v4 1/3] client/player.c: " Silviu Florian Barbulescu
2024-01-10 17:33 ` bluez.test.bot
2024-01-10 16:58 [PATCH v5 1/3] client/player.c: " Silviu Florian Barbulescu
2024-01-10 18:27 ` 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=653aa5bd.050a0220.81f15.2562@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=silviu.barbulescu@nxp.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 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.