From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [BlueZ,1/2] a2dp: disallow multiple SetConfiguration to same local SEP
Date: Sun, 05 Jun 2022 07:21:24 -0700 (PDT) [thread overview]
Message-ID: <629cbbe4.1c69fb81.c63d3.3037@mx.google.com> (raw)
In-Reply-To: <20220605122927.110627-1-pav@iki.fi>
[-- 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=647442
---Test result---
Test Summary:
CheckPatch PASS 2.91 seconds
GitLint PASS 1.84 seconds
Prep - Setup ELL PASS 43.36 seconds
Build - Prep PASS 0.69 seconds
Build - Configure PASS 8.69 seconds
Build - Make PASS 1280.99 seconds
Make Check PASS 11.99 seconds
Make Check w/Valgrind PASS 445.82 seconds
Make Distcheck PASS 233.21 seconds
Build w/ext ELL - Configure PASS 8.80 seconds
Build w/ext ELL - Make PASS 1287.67 seconds
Incremental Build with patchesPASS 2641.51 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-06-05 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 12:29 [PATCH BlueZ 1/2] a2dp: disallow multiple SetConfiguration to same local SEP Pauli Virtanen
2022-06-05 12:29 ` [PATCH BlueZ 2/2] a2dp: error return paths in a2dp_reconfig must free allocated setup Pauli Virtanen
2022-06-05 14:21 ` bluez.test.bot [this message]
2022-06-07 5:33 ` [PATCH BlueZ 1/2] a2dp: disallow multiple SetConfiguration to same local SEP Luiz Augusto von Dentz
2022-06-07 7:44 ` Pauli Virtanen
2022-06-07 19:28 ` Luiz Augusto von Dentz
2022-06-13 18:10 ` patchwork-bot+bluetooth
2022-06-13 21:02 ` Luiz Augusto von Dentz
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=629cbbe4.1c69fb81.c63d3.3037@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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.