From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, sean.wang@mediatek.com
Subject: RE: [v5,1/3] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding
Date: Tue, 02 May 2023 16:32:26 -0700 (PDT) [thread overview]
Message-ID: <64519d8a.620a0220.73244.3d2a@mx.google.com> (raw)
In-Reply-To: <c90f4606c85f5862e2e3e1dc330af4ac95f2bc9f.1683065391.git.objelf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2075 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=744518
---Test result---
Test Summary:
CheckPatch PASS 2.52 seconds
GitLint FAIL 1.07 seconds
SubjectPrefix PASS 0.27 seconds
BuildKernel PASS 32.25 seconds
CheckAllWarning PASS 35.15 seconds
CheckSparse PASS 39.68 seconds
CheckSmatch PASS 110.69 seconds
BuildKernel32 PASS 30.98 seconds
TestRunnerSetup PASS 440.96 seconds
TestRunner_l2cap-tester PASS 16.53 seconds
TestRunner_iso-tester PASS 20.25 seconds
TestRunner_bnep-tester PASS 5.29 seconds
TestRunner_mgmt-tester PASS 112.02 seconds
TestRunner_rfcomm-tester PASS 8.47 seconds
TestRunner_sco-tester PASS 7.87 seconds
TestRunner_ioctl-tester PASS 9.17 seconds
TestRunner_mesh-tester PASS 6.66 seconds
TestRunner_smp-tester PASS 7.74 seconds
TestRunner_userchan-tester PASS 5.50 seconds
IncrementalBuild PASS 40.80 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v5,1/3] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding
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
1: T1 Title exceeds max length (82>80): "[v5,1/3] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding"
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-05-02 23:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 23:02 [PATCH v5 1/3] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding sean.wang
2023-05-02 23:02 ` [PATCH v5 2/3] Bluetooth: btmtk: introduce btmtk reset work sean.wang
2023-05-02 23:02 ` [PATCH v5 3/3] Bluetooth: btusb: mediatek: add MediaTek devcoredump support sean.wang
2023-05-03 9:42 ` kernel test robot
2023-05-08 19:54 ` Luiz Augusto von Dentz
2023-05-02 23:32 ` 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=64519d8a.620a0220.73244.3d2a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sean.wang@mediatek.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.