From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, max.chou@realtek.com
Subject: RE: [v2] Bluetooth: btrtl: Firmware format v2 support
Date: Thu, 02 Feb 2023 04:42:03 -0800 (PST) [thread overview]
Message-ID: <63dbaf9b.c80a0220.30d2e.7d9c@mx.google.com> (raw)
In-Reply-To: <20230202114614.53907-1-max.chou@realtek.com>
[-- Attachment #1: Type: text/plain, Size: 2629 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=718117
---Test result---
Test Summary:
CheckPatch PASS 1.47 seconds
GitLint FAIL 0.59 seconds
SubjectPrefix PASS 0.12 seconds
BuildKernel PASS 32.41 seconds
CheckAllWarning PASS 34.42 seconds
CheckSparse WARNING 39.28 seconds
CheckSmatch WARNING 107.00 seconds
BuildKernel32 PASS 30.51 seconds
TestRunnerSetup PASS 438.93 seconds
TestRunner_l2cap-tester PASS 16.68 seconds
TestRunner_iso-tester PASS 17.51 seconds
TestRunner_bnep-tester PASS 5.83 seconds
TestRunner_mgmt-tester PASS 113.14 seconds
TestRunner_rfcomm-tester PASS 9.24 seconds
TestRunner_sco-tester PASS 8.45 seconds
TestRunner_ioctl-tester PASS 9.90 seconds
TestRunner_mesh-tester PASS 7.34 seconds
TestRunner_smp-tester PASS 8.30 seconds
TestRunner_userchan-tester PASS 6.11 seconds
IncrementalBuild PASS 28.50 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v2] Bluetooth: btrtl: Firmware format v2 support
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
24: B1 Line exceeds max length (83>80): "> I rather use an skb for parsing the data instead of parsing via pointer directly,"
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
drivers/bluetooth/btrtl.c:882:22: warning: cast to restricted __le16drivers/bluetooth/btrtl.c:888:27: warning: cast to restricted __le16drivers/bluetooth/btrtl.c: note: in included file:drivers/bluetooth/btrtl.h:47:45: warning: array of flexible structures
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
drivers/bluetooth/btrtl.c: note: in included file:drivers/bluetooth/btrtl.h:47:45: warning: array of flexible structures
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-02-02 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 11:46 [PATCH v2] Bluetooth: btrtl: Firmware format v2 support max.chou
2023-02-02 12:42 ` bluez.test.bot [this message]
2023-02-02 22:03 ` [v2] " Luiz Augusto von Dentz
2023-02-06 3:27 ` Max Chou
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=63dbaf9b.c80a0220.30d2e.7d9c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=max.chou@realtek.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.