From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, lee.jones@linaro.org
Subject: RE: [RESEND,1/1] Bluetooth: Use chan_list_lock to protect the whole put/destroy invokation
Date: Wed, 22 Jun 2022 02:15:49 -0700 (PDT) [thread overview]
Message-ID: <62b2ddc5.1c69fb81.24421.3c54@mx.google.com> (raw)
In-Reply-To: <20220622082716.478486-1-lee.jones@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2588 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=652672
---Test result---
Test Summary:
CheckPatch FAIL 1.22 seconds
GitLint FAIL 0.73 seconds
SubjectPrefix PASS 0.63 seconds
BuildKernel PASS 41.39 seconds
BuildKernel32 PASS 36.81 seconds
Incremental Build with patchesPASS 47.55 seconds
TestRunner: Setup PASS 648.42 seconds
TestRunner: l2cap-tester PASS 15.98 seconds
TestRunner: bnep-tester PASS 5.24 seconds
TestRunner: mgmt-tester PASS 96.63 seconds
TestRunner: rfcomm-tester PASS 8.55 seconds
TestRunner: sco-tester PASS 8.32 seconds
TestRunner: smp-tester PASS 8.43 seconds
TestRunner: userchan-tester PASS 5.41 seconds
Details
##############################
Test: CheckPatch - FAIL - 1.22 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
[RESEND,1/1] Bluetooth: Use chan_list_lock to protect the whole put/destroy invokation\WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#96:
CPU: 4 PID: 705 Comm: kworker/u17:14 Tainted: G S W 4.14.234-00003-g1fb6d0bd49a4-dirty #28
total: 0 errors, 1 warnings, 0 checks, 18 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/12890300.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 - 0.73 seconds
Run gitlint with rule in .gitlint
[RESEND,1/1] Bluetooth: Use chan_list_lock to protect the whole put/destroy invokation
1: T1 Title exceeds max length (86>80): "[RESEND,1/1] Bluetooth: Use chan_list_lock to protect the whole put/destroy invokation"
12: B1 Line exceeds max length (103>80): " CPU: 4 PID: 705 Comm: kworker/u17:14 Tainted: G S W 4.14.234-00003-g1fb6d0bd49a4-dirty #28"
13: B1 Line exceeds max length (99>80): " Hardware name: Qualcomm Technologies, Inc. SM8150 V2 PM8150 Google Inc. MSM sm8150 Flame DVT (DT)"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-06-22 9:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 8:27 [RESEND 1/1] Bluetooth: Use chan_list_lock to protect the whole put/destroy invokation Lee Jones
2022-06-22 9:15 ` bluez.test.bot [this message]
2022-06-27 14:17 ` Lee Jones
2022-06-27 14:41 ` Eric Dumazet
2022-06-27 23:39 ` Luiz Augusto von Dentz
2022-06-28 18:36 ` Luiz Augusto von Dentz
2022-06-29 15:28 ` Lee Jones
2022-07-05 17:21 ` Luiz Augusto von Dentz
2022-07-06 10:53 ` Lee Jones
2022-07-06 20:36 ` Luiz Augusto von Dentz
2022-07-06 20:58 ` Luiz Augusto von Dentz
2022-07-14 17:46 ` Luiz Augusto von Dentz
2022-07-15 7:28 ` Lee Jones
2022-07-20 11:52 ` Lee Jones
2022-07-20 17:10 ` Luiz Augusto von Dentz
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=62b2ddc5.1c69fb81.24421.3c54@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-bluetooth@vger.kernel.org \
/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).