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, 17 Nov 2022 23:29:46 -0800 (PST) [thread overview]
Message-ID: <6377346a.050a0220.89b9d.716b@mx.google.com> (raw)
In-Reply-To: <1666868760-4680-1-git-send-email-quic_zijuhu@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 1258 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 0.56 seconds
GitLint PASS 0.28 seconds
SubjectPrefix PASS 0.09 seconds
BuildKernel PASS 33.07 seconds
BuildKernel32 PASS 30.09 seconds
TestRunnerSetup PASS 416.44 seconds
TestRunner_l2cap-tester PASS 16.06 seconds
TestRunner_iso-tester PASS 15.46 seconds
TestRunner_bnep-tester PASS 5.48 seconds
TestRunner_mgmt-tester PASS 104.89 seconds
TestRunner_rfcomm-tester PASS 9.30 seconds
TestRunner_sco-tester PASS 8.79 seconds
TestRunner_ioctl-tester PASS 10.05 seconds
TestRunner_mesh-tester PASS 6.91 seconds
TestRunner_smp-tester PASS 8.58 seconds
TestRunner_userchan-tester PASS 5.74 seconds
IncrementalBuild PASS 30.76 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-11-18 7:29 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 ` [v1] " bluez.test.bot
2022-11-18 3:52 ` 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 [this message]
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=6377346a.050a0220.89b9d.716b@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