From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_saluvala@quicinc.com
Subject: RE: [v2] arm64: dts: qcom: sc7280: setting the vddio supply for Bluetooth node on CRD
Date: Tue, 08 Feb 2022 03:59:25 -0800 (PST) [thread overview]
Message-ID: <62025b1d.1c69fb81.db2a6.61aa@mx.google.com> (raw)
In-Reply-To: <1644318803-14950-1-git-send-email-quic_saluvala@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 1576 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=612157
---Test result---
Test Summary:
CheckPatch PASS 0.71 seconds
GitLint FAIL 0.45 seconds
SubjectPrefix FAIL 0.25 seconds
BuildKernel PASS 37.92 seconds
BuildKernel32 PASS 33.43 seconds
Incremental Build with patchesPASS 43.83 seconds
TestRunner: Setup PASS 600.88 seconds
TestRunner: l2cap-tester PASS 15.78 seconds
TestRunner: bnep-tester PASS 6.85 seconds
TestRunner: mgmt-tester PASS 124.22 seconds
TestRunner: rfcomm-tester PASS 8.51 seconds
TestRunner: sco-tester PASS 8.80 seconds
TestRunner: smp-tester PASS 8.71 seconds
TestRunner: userchan-tester PASS 7.12 seconds
Details
##############################
Test: GitLint - FAIL - 0.45 seconds
Run gitlint with rule in .gitlint
[v2] arm64: dts: qcom: sc7280: setting the vddio supply for Bluetooth node on CRD
1: T1 Title exceeds max length (81>80): "[v2] arm64: dts: qcom: sc7280: setting the vddio supply for Bluetooth node on CRD"
##############################
Test: SubjectPrefix - FAIL - 0.25 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-02-08 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 11:13 [PATCH v2] arm64: dts: qcom: sc7280: setting the vddio supply for Bluetooth node on CRD Sai Teja Aluvala
2022-02-08 11:59 ` bluez.test.bot [this message]
2022-02-09 9:52 ` kernel test robot
2022-02-11 0:39 ` Bjorn Andersson
2022-02-11 13:49 ` 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=62025b1d.1c69fb81.db2a6.61aa@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 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.