From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, Mario.Limonciello@amd.com
Subject: RE: Bluetooth: btusb: Add new PID/VID 0489:e0f2 for MT7921
Date: Wed, 14 Dec 2022 18:41:15 -0800 (PST) [thread overview]
Message-ID: <639a894b.050a0220.43c2a.4c5e@mx.google.com> (raw)
In-Reply-To: <20221215021854.1429-1-mario.limonciello@amd.com>
[-- Attachment #1: Type: text/plain, Size: 1365 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=704649
---Test result---
Test Summary:
CheckPatch PASS 0.68 seconds
GitLint PASS 0.34 seconds
SubjectPrefix PASS 0.12 seconds
BuildKernel PASS 32.90 seconds
CheckAllWarning PASS 35.19 seconds
CheckSparse PASS 40.13 seconds
BuildKernel32 PASS 30.81 seconds
TestRunnerSetup PASS 432.78 seconds
TestRunner_l2cap-tester PASS 16.26 seconds
TestRunner_iso-tester PASS 16.63 seconds
TestRunner_bnep-tester PASS 5.61 seconds
TestRunner_mgmt-tester PASS 107.32 seconds
TestRunner_rfcomm-tester PASS 8.78 seconds
TestRunner_sco-tester PASS 8.10 seconds
TestRunner_ioctl-tester PASS 9.44 seconds
TestRunner_mesh-tester PASS 7.02 seconds
TestRunner_smp-tester PASS 8.01 seconds
TestRunner_userchan-tester PASS 5.82 seconds
IncrementalBuild PASS 28.46 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-12-15 2:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 2:18 [PATCH] Bluetooth: btusb: Add new PID/VID 0489:e0f2 for MT7921 Mario Limonciello
2022-12-15 2:18 ` Mario Limonciello
2022-12-15 2:41 ` bluez.test.bot [this message]
2023-01-03 14:58 ` Limonciello, Mario
2023-01-03 14:58 ` Limonciello, Mario
2023-01-03 22:40 ` patchwork-bot+bluetooth
2023-01-03 22:40 ` patchwork-bot+bluetooth
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=639a894b.050a0220.43c2a.4c5e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=Mario.Limonciello@amd.com \
--cc=linux-bluetooth@vger.kernel.org \
/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.