From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: Remove POLLOUT check before bcast defer accept
Date: Wed, 27 Mar 2024 11:10:51 -0700 (PDT) [thread overview]
Message-ID: <6604612b.050a0220.23bac.7d18@mx.google.com> (raw)
In-Reply-To: <20240327161019.3078-2-iulia.tanasescu@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=838961
---Test result---
Test Summary:
CheckPatch PASS 0.90 seconds
GitLint PASS 0.61 seconds
BuildEll PASS 24.41 seconds
BluezMake PASS 1708.45 seconds
MakeCheck PASS 12.78 seconds
MakeDistcheck PASS 180.35 seconds
CheckValgrind PASS 245.99 seconds
CheckSmatch PASS 362.14 seconds
bluezmakeextell PASS 120.19 seconds
IncrementalBuild PASS 3072.32 seconds
ScanBuild PASS 1022.92 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-03-27 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 16:10 [PATCH BlueZ 0/2] Remove POLLOUT check before bcast defer accept Iulia Tanasescu
2024-03-27 16:10 ` [PATCH BlueZ 1/2] btio: Remove POLLOUT check from bt_io_bcast_accept Iulia Tanasescu
2024-03-27 18:10 ` bluez.test.bot [this message]
2024-03-27 16:10 ` [PATCH BlueZ 2/2] iso-tester: Separate iso_defer_accept into dedicated functions Iulia Tanasescu
2024-03-27 16:50 ` Luiz Augusto von Dentz
2024-03-27 17:48 ` Pauli Virtanen
2024-03-28 13:07 ` Iulia Tanasescu
2024-03-28 14:40 ` [PATCH BlueZ 0/2] Remove POLLOUT check before bcast defer accept 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=6604612b.050a0220.23bac.7d18@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).