From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yepuri.siddu@oss.qualcomm.com
Subject: RE: [1/4] dt-bindings: bluetooth: qcom,qcc2072-bt: add bindings for QCC2072
Date: Fri, 29 May 2026 13:29:49 -0700 (PDT) [thread overview]
Message-ID: <6a19f73d.143d05a0.bd374.a96b@mx.google.com> (raw)
In-Reply-To: <20260529175342.3363935-1-yepuri.siddu@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 2158 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=1103053
---Test result---
Test Summary:
CheckPatch FAIL 3.60 seconds
VerifyFixes PASS 4.63 seconds
VerifySignedoff PASS 0.72 seconds
GitLint FAIL 1.64 seconds
SubjectPrefix FAIL 0.44 seconds
BuildKernel PASS 25.11 seconds
CheckAllWarning PASS 28.10 seconds
CheckSparse PASS 26.48 seconds
BuildKernel32 PASS 24.42 seconds
TestRunnerSetup PASS 526.63 seconds
IncrementalBuild PASS 28.03 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[1/4] dt-bindings: bluetooth: qcom,qcc2072-bt: add bindings for QCC2072
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#176:
new file mode 100644
total: 0 errors, 1 warnings, 38 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/patch/14601841.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[1/4] dt-bindings: bluetooth: qcom,qcc2072-bt: add bindings for QCC2072
15: B1 Line exceeds max length (88>80): " create mode 100644 Documentation/devicetree/bindings/net/bluetooth/qcom,qcc2072-bt.yaml"
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
https://github.com/bluez/bluetooth-next/pull/258
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-05-29 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 17:53 [PATCH 1/4] dt-bindings: bluetooth: qcom,qcc2072-bt: add bindings for QCC2072 Yepuri Siddu
2026-05-29 20:29 ` bluez.test.bot [this message]
2026-05-30 12:34 ` Krzysztof Kozlowski
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=6a19f73d.143d05a0.bd374.a96b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=yepuri.siddu@oss.qualcomm.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