From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_zijuhu@quicinc.com
Subject: RE: [v1] Bluetooth: Fix cvsd sco setup failure
Date: Thu, 14 Jul 2022 01:00:43 -0700 (PDT) [thread overview]
Message-ID: <62cfcd2b.1c69fb81.13eb3.1c18@mx.google.com> (raw)
In-Reply-To: <1657782880-28234-1-git-send-email-quic_zijuhu@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 1097 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=659570
---Test result---
Test Summary:
CheckPatch PASS 1.46 seconds
GitLint PASS 0.71 seconds
SubjectPrefix PASS 0.66 seconds
BuildKernel PASS 32.14 seconds
BuildKernel32 PASS 27.75 seconds
Incremental Build with patchesPASS 38.14 seconds
TestRunner: Setup PASS 477.78 seconds
TestRunner: l2cap-tester PASS 17.07 seconds
TestRunner: bnep-tester PASS 6.08 seconds
TestRunner: mgmt-tester PASS 103.92 seconds
TestRunner: rfcomm-tester PASS 9.45 seconds
TestRunner: sco-tester PASS 9.10 seconds
TestRunner: smp-tester PASS 9.21 seconds
TestRunner: userchan-tester PASS 6.10 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-07-14 8:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 7:14 [PATCH v1] Bluetooth: Fix cvsd sco setup failure Zijun Hu
2022-07-14 8:00 ` bluez.test.bot [this message]
2022-07-14 21:24 ` Luiz Augusto von Dentz
2022-07-15 3:31 ` quic_zijuhu
2022-07-15 4:21 ` Luiz Augusto von Dentz
2022-07-15 5:25 ` quic_zijuhu
2022-07-18 23:59 ` Luiz Augusto von Dentz
2022-07-19 3:37 ` quic_zijuhu
-- strict thread matches above, loose matches on Subject: below --
2022-06-09 11:03 [PATCH v1] Bluetooth: Fix CVSD SCO " Zijun Hu
2022-06-09 12:00 ` [v1] " 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=62cfcd2b.1c69fb81.13eb3.1c18@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=quic_zijuhu@quicinc.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;
as well as URLs for NNTP newsgroup(s).