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, 29 Oct 2022 11:10:52 -0700 (PDT) [thread overview]
Message-ID: <635d6cac.050a0220.cda55.287d@mx.google.com> (raw)
In-Reply-To: <OS3P286MB2597E5DC0322DE5839B85D7698359@OS3P286MB2597.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=690163
---Test result---
Test Summary:
CheckPatch PASS 1.50 seconds
GitLint PASS 0.83 seconds
SubjectPrefix PASS 0.67 seconds
BuildKernel PASS 39.42 seconds
BuildKernel32 PASS 35.36 seconds
Incremental Build with patchesPASS 51.42 seconds
TestRunner: Setup PASS 592.71 seconds
TestRunner: l2cap-tester PASS 19.18 seconds
TestRunner: iso-tester PASS 18.88 seconds
TestRunner: bnep-tester PASS 7.32 seconds
TestRunner: mgmt-tester PASS 116.55 seconds
TestRunner: rfcomm-tester PASS 11.81 seconds
TestRunner: sco-tester PASS 11.01 seconds
TestRunner: ioctl-tester PASS 12.45 seconds
TestRunner: mesh-tester PASS 9.02 seconds
TestRunner: smp-tester PASS 10.79 seconds
TestRunner: userchan-tester PASS 7.97 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-10-29 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 17:22 [RESEND PATCH v3] Bluetooth: btusb: Add more device IDs for WCN6855 Shengyu Qu
2022-10-29 18:10 ` bluez.test.bot [this message]
2022-10-31 23:10 ` patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2022-10-22 19:25 Shengyu Qu
2022-10-22 20:08 ` [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=635d6cac.050a0220.cda55.287d@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).