From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_saluvala@quicinc.com
Subject: RE: [v4] Bluetooth: arm64: dts: qcom: sc7280: Add IO regulator handler in SC7280 CRD platforms
Date: Wed, 20 Apr 2022 06:41:26 -0700 (PDT) [thread overview]
Message-ID: <62600d86.1c69fb81.ed5ab.d454@mx.google.com> (raw)
In-Reply-To: <1650458740-16957-1-git-send-email-quic_saluvala@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 1435 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=633779
---Test result---
Test Summary:
CheckPatch PASS 1.75 seconds
GitLint FAIL 1.03 seconds
SubjectPrefix PASS 0.85 seconds
BuildKernel PASS 44.45 seconds
BuildKernel32 PASS 39.01 seconds
Incremental Build with patchesPASS 53.14 seconds
TestRunner: Setup PASS 673.40 seconds
TestRunner: l2cap-tester PASS 22.58 seconds
TestRunner: bnep-tester PASS 9.19 seconds
TestRunner: mgmt-tester PASS 144.05 seconds
TestRunner: rfcomm-tester PASS 13.57 seconds
TestRunner: sco-tester PASS 13.22 seconds
TestRunner: smp-tester PASS 12.82 seconds
TestRunner: userchan-tester PASS 9.32 seconds
Details
##############################
Test: GitLint - FAIL - 1.03 seconds
Run gitlint with rule in .gitlint
[v4] Bluetooth: arm64: dts: qcom: sc7280: Add IO regulator handler in SC7280 CRD platforms
1: T1 Title exceeds max length (90>80): "[v4] Bluetooth: arm64: dts: qcom: sc7280: Add IO regulator handler in SC7280 CRD platforms"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-04-20 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 12:45 [PATCH v4] Bluetooth: arm64: dts: qcom: sc7280: Add IO regulator handler in SC7280 CRD platforms Sai Teja Aluvala
2022-04-20 13:41 ` bluez.test.bot [this message]
2022-04-20 19:06 ` Matthias Kaehlcke
2022-04-23 15:35 ` Bjorn Andersson
2022-04-27 5:33 ` Sai Teja Aluvala (Temp) (QUIC)
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=62600d86.1c69fb81.ed5ab.d454@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=quic_saluvala@quicinc.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).