From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, minhuadotchen@gmail.com
Subject: RE: Bluetooth: btqca: use le32_to_cpu for ver.soc_id
Date: Thu, 18 May 2023 18:15:41 -0700 (PDT) [thread overview]
Message-ID: <6466cdbd.050a0220.8719f.4ccc@mx.google.com> (raw)
In-Reply-To: <20230519002544.3695-1-minhuadotchen@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2048 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=749075
---Test result---
Test Summary:
CheckPatch PASS 0.73 seconds
GitLint FAIL 0.58 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 38.18 seconds
CheckAllWarning PASS 41.17 seconds
CheckSparse PASS 46.66 seconds
CheckSmatch PASS 126.18 seconds
BuildKernel32 PASS 36.45 seconds
TestRunnerSetup PASS 526.26 seconds
TestRunner_l2cap-tester PASS 19.18 seconds
TestRunner_iso-tester PASS 24.81 seconds
TestRunner_bnep-tester PASS 6.70 seconds
TestRunner_mgmt-tester PASS 132.74 seconds
TestRunner_rfcomm-tester PASS 10.34 seconds
TestRunner_sco-tester PASS 9.58 seconds
TestRunner_ioctl-tester PASS 11.34 seconds
TestRunner_mesh-tester PASS 8.23 seconds
TestRunner_smp-tester PASS 9.25 seconds
TestRunner_userchan-tester PASS 6.77 seconds
IncrementalBuild PASS 35.08 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: btqca: use le32_to_cpu for ver.soc_id
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
6: B1 Line exceeds max length (88>80): "drivers/bluetooth/btqca.c:640:24: sparse: warning: restricted __le32 degrades to integer"
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-05-19 1:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 0:25 [PATCH] Bluetooth: btqca: use le32_to_cpu for ver.soc_id Min-Hua Chen
2023-05-19 1:15 ` 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=6466cdbd.050a0220.8719f.4ccc@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=minhuadotchen@gmail.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).