From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_zijuhu@quicinc.com
Subject: RE: [v1] Bluetooth: btusb: Fix enable failure for a CSR BT dongle
Date: Thu, 27 Oct 2022 05:06:46 -0700 (PDT) [thread overview]
Message-ID: <635a7456.9d0a0220.a0414.11c9@mx.google.com> (raw)
In-Reply-To: <1666868760-4680-1-git-send-email-quic_zijuhu@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 1261 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=689388
---Test result---
Test Summary:
CheckPatch PASS 1.31 seconds
GitLint PASS 0.79 seconds
SubjectPrefix PASS 0.60 seconds
BuildKernel PASS 40.13 seconds
BuildKernel32 PASS 36.08 seconds
Incremental Build with patchesPASS 54.02 seconds
TestRunner: Setup PASS 608.14 seconds
TestRunner: l2cap-tester PASS 19.54 seconds
TestRunner: iso-tester PASS 19.79 seconds
TestRunner: bnep-tester PASS 7.61 seconds
TestRunner: mgmt-tester PASS 119.94 seconds
TestRunner: rfcomm-tester PASS 11.91 seconds
TestRunner: sco-tester PASS 11.06 seconds
TestRunner: ioctl-tester PASS 12.73 seconds
TestRunner: mesh-tester PASS 9.40 seconds
TestRunner: smp-tester PASS 11.09 seconds
TestRunner: userchan-tester PASS 7.88 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-10-27 12:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 11:06 [PATCH v1] Bluetooth: btusb: Fix enable failure for a CSR BT dongle Zijun Hu
2022-10-27 11:18 ` Paul Menzel
2022-10-28 2:57 ` quic_zijuhu
2022-10-27 12:06 ` bluez.test.bot [this message]
2022-11-18 3:52 ` [v1] " bluez.test.bot
2022-11-18 4:34 ` bluez.test.bot
2022-11-18 5:29 ` bluez.test.bot
2022-11-18 6:37 ` bluez.test.bot
2022-11-18 7:29 ` bluez.test.bot
2022-11-18 8:35 ` bluez.test.bot
2022-11-18 9:33 ` bluez.test.bot
2022-11-19 3:55 ` bluez.test.bot
2022-11-19 5:02 ` 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=635a7456.9d0a0220.a0414.11c9@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 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.