From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, sean.wang@mediatek.com
Subject: RE: [RESEND,v3] Bluetooth: btusb: mediatek: fix WMT command failure during runtime suspend
Date: Fri, 29 Jul 2022 09:11:56 -0700 (PDT) [thread overview]
Message-ID: <62e406cc.a70a0220.181a1.4afc@mx.google.com> (raw)
In-Reply-To: <96994209776d6643585426b4341bbe2dcd9f5116.1659105441.git.objelf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1425 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=664093
---Test result---
Test Summary:
CheckPatch PASS 1.81 seconds
GitLint FAIL 0.55 seconds
SubjectPrefix PASS 0.42 seconds
BuildKernel PASS 39.40 seconds
BuildKernel32 PASS 34.29 seconds
Incremental Build with patchesPASS 46.34 seconds
TestRunner: Setup PASS 563.81 seconds
TestRunner: l2cap-tester PASS 17.85 seconds
TestRunner: bnep-tester PASS 6.79 seconds
TestRunner: mgmt-tester PASS 105.84 seconds
TestRunner: rfcomm-tester PASS 10.14 seconds
TestRunner: sco-tester PASS 9.90 seconds
TestRunner: smp-tester PASS 9.74 seconds
TestRunner: userchan-tester PASS 6.81 seconds
Details
##############################
Test: GitLint - FAIL - 0.55 seconds
Run gitlint with rule in .gitlint
[RESEND,v3] Bluetooth: btusb: mediatek: fix WMT command failure during runtime suspend
1: T1 Title exceeds max length (86>80): "[RESEND,v3] Bluetooth: btusb: mediatek: fix WMT command failure during runtime suspend"
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2022-07-29 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 14:43 [PATCH RESEND v3] Bluetooth: btusb: mediatek: fix WMT command failure during runtime suspend sean.wang
2022-07-29 16:11 ` bluez.test.bot [this message]
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=62e406cc.a70a0220.181a1.4afc@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sean.wang@mediatek.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