From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, wiagn233@outlook.com
Subject: RE: [RESEND,v3] Bluetooth: btusb: Add more device IDs for WCN6855
Date: Sat, 22 Oct 2022 13:08:38 -0700 (PDT) [thread overview]
Message-ID: <63544dc6.a70a0220.5a6c7.2147@mx.google.com> (raw)
In-Reply-To: <TY3P286MB2611D3672C5664AB862E10E8982C9@TY3P286MB2611.JPNP286.PROD.OUTLOOK.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=687881
---Test result---
Test Summary:
CheckPatch PASS 1.11 seconds
GitLint PASS 0.49 seconds
SubjectPrefix PASS 0.35 seconds
BuildKernel PASS 44.94 seconds
BuildKernel32 PASS 40.09 seconds
Incremental Build with patchesPASS 59.89 seconds
TestRunner: Setup PASS 663.15 seconds
TestRunner: l2cap-tester PASS 21.06 seconds
TestRunner: iso-tester PASS 21.36 seconds
TestRunner: bnep-tester PASS 8.18 seconds
TestRunner: mgmt-tester PASS 133.28 seconds
TestRunner: rfcomm-tester PASS 13.00 seconds
TestRunner: sco-tester PASS 11.90 seconds
TestRunner: ioctl-tester PASS 13.79 seconds
TestRunner: mesh-tester PASS 9.99 seconds
TestRunner: smp-tester PASS 11.74 seconds
TestRunner: userchan-tester PASS 8.58 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-10-22 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 19:25 [RESEND PATCH v3] Bluetooth: btusb: Add more device IDs for WCN6855 Shengyu Qu
2022-10-22 20:08 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-29 17:22 Shengyu Qu
2022-10-29 18:10 ` [RESEND,v3] " 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=63544dc6.a70a0220.5a6c7.2147@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=wiagn233@outlook.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).