From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_saluvala@quicinc.com
Subject: RE: [v1] arm64: dts: qcom: sc7280: Add bluetooth node on SC7280 crd board
Date: Sun, 06 Feb 2022 23:06:39 -0800 (PST) [thread overview]
Message-ID: <6200c4ff.1c69fb81.674e1.7a25@mx.google.com> (raw)
In-Reply-To: <1644207878-19839-1-git-send-email-quic_saluvala@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 1267 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=611723
---Test result---
Test Summary:
CheckPatch PASS 1.68 seconds
GitLint PASS 1.02 seconds
SubjectPrefix FAIL 0.90 seconds
BuildKernel PASS 33.70 seconds
BuildKernel32 PASS 29.33 seconds
Incremental Build with patchesPASS 40.42 seconds
TestRunner: Setup PASS 539.08 seconds
TestRunner: l2cap-tester PASS 14.95 seconds
TestRunner: bnep-tester PASS 7.10 seconds
TestRunner: mgmt-tester PASS 122.04 seconds
TestRunner: rfcomm-tester PASS 8.38 seconds
TestRunner: sco-tester PASS 8.60 seconds
TestRunner: smp-tester PASS 8.68 seconds
TestRunner: userchan-tester PASS 7.49 seconds
Details
##############################
Test: SubjectPrefix - FAIL - 0.90 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-02-07 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 4:24 [PATCH v1] arm64: dts: qcom: sc7280: Add bluetooth node on SC7280 crd board Sai Teja Aluvala
2022-02-07 7:06 ` bluez.test.bot [this message]
2022-02-07 8:42 ` Sai Teja Aluvala (Temp) (QUIC)
2022-02-07 11:12 ` kernel test robot
2022-02-07 17:13 ` Matthias Kaehlcke
2022-02-08 4:13 ` 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=6200c4ff.1c69fb81.674e1.7a25@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