From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_tjiang@quicinc.com
Subject: RE: [v4] Bluetooth: hci_qca: Add support for Qualcomm Bluetooth SoC QCA2066
Date: Wed, 17 May 2023 04:34:42 -0700 (PDT) [thread overview]
Message-ID: <6464bbd2.170a0220.728d9.b2ae@mx.google.com> (raw)
In-Reply-To: <20230517104426.14055-1-quic_tjiang@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 2539 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=748375
---Test result---
Test Summary:
CheckPatch FAIL 1.56 seconds
GitLint PASS 0.26 seconds
SubjectPrefix PASS 0.07 seconds
BuildKernel PASS 39.34 seconds
CheckAllWarning PASS 43.29 seconds
CheckSparse WARNING 48.95 seconds
CheckSmatch PASS 132.11 seconds
BuildKernel32 PASS 38.76 seconds
TestRunnerSetup PASS 542.27 seconds
TestRunner_l2cap-tester PASS 19.88 seconds
TestRunner_iso-tester PASS 25.41 seconds
TestRunner_bnep-tester PASS 6.78 seconds
TestRunner_mgmt-tester PASS 132.31 seconds
TestRunner_rfcomm-tester PASS 10.57 seconds
TestRunner_sco-tester PASS 9.79 seconds
TestRunner_ioctl-tester PASS 11.54 seconds
TestRunner_mesh-tester PASS 8.51 seconds
TestRunner_smp-tester PASS 9.73 seconds
TestRunner_userchan-tester PASS 7.21 seconds
IncrementalBuild PASS 36.58 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v4] Bluetooth: hci_qca: Add support for Qualcomm Bluetooth SoC QCA2066
WARNING: DT compatible string "qcom,qca2066-bt" appears un-documented -- check ./Documentation/devicetree/bindings/
#279: FILE: drivers/bluetooth/hci_qca.c:2372:
+ { .compatible = "qcom,qca2066-bt", .data = &qca_soc_data_qca2066},
total: 0 errors, 1 warnings, 160 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/src/13244615.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: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
drivers/bluetooth/btqca.c:629:17: warning: restricted __le32 degrades to integerdrivers/bluetooth/btqca.c:712:24: warning: restricted __le32 degrades to integer
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-05-17 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 10:44 [PATCH v4] Bluetooth: hci_qca: Add support for Qualcomm Bluetooth SoC QCA2066 Tim Jiang
2023-05-17 11:34 ` 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=6464bbd2.170a0220.728d9.b2ae@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=quic_tjiang@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.