From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, andy.chi@canonical.com
Subject: RE: Bluteooth: btusb: Add a new VID/PID 0489/e0f2 for MT7922
Date: Sun, 27 Nov 2022 23:01:44 -0800 (PST) [thread overview]
Message-ID: <63845cd8.170a0220.7ff72.ae0c@mx.google.com> (raw)
In-Reply-To: <20221128063000.41036-1-andy.chi@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1433 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=699572
---Test result---
Test Summary:
CheckPatch PASS 0.50 seconds
GitLint PASS 0.22 seconds
SubjectPrefix FAIL 0.43 seconds
BuildKernel PASS 34.44 seconds
BuildKernel32 PASS 31.53 seconds
TestRunnerSetup PASS 425.10 seconds
TestRunner_l2cap-tester PASS 16.03 seconds
TestRunner_iso-tester PASS 15.75 seconds
TestRunner_bnep-tester PASS 5.53 seconds
TestRunner_mgmt-tester PASS 106.76 seconds
TestRunner_rfcomm-tester PASS 9.52 seconds
TestRunner_sco-tester PASS 8.86 seconds
TestRunner_ioctl-tester PASS 10.23 seconds
TestRunner_mesh-tester PASS 7.09 seconds
TestRunner_smp-tester PASS 8.69 seconds
TestRunner_userchan-tester PASS 5.78 seconds
IncrementalBuild PASS 32.16 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-11-28 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 6:30 [PATCH] Bluteooth: btusb: Add a new VID/PID 0489/e0f2 for MT7922 Andy Chi
2022-11-28 7:01 ` bluez.test.bot [this message]
2022-11-28 7:49 ` [PATCH v2] Bluetooth: " Andy Chi
2022-11-29 21:10 ` patchwork-bot+bluetooth
2022-11-29 21:10 ` [PATCH] Bluteooth: " 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=63845cd8.170a0220.7ff72.ae0c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=andy.chi@canonical.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 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).