From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, schspa@gmail.com
Subject: RE: Bluetooth: When HCI work queue is drained, only queue chained work.
Date: Tue, 31 May 2022 12:11:58 -0700 (PDT) [thread overview]
Message-ID: <6296687e.1c69fb81.b9736.0cf2@mx.google.com> (raw)
In-Reply-To: <20220531184124.20577-1-schspa@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1516 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=646337
---Test result---
Test Summary:
CheckPatch PASS 2.03 seconds
GitLint FAIL 1.10 seconds
SubjectPrefix PASS 0.83 seconds
BuildKernel PASS 32.53 seconds
BuildKernel32 PASS 27.94 seconds
Incremental Build with patchesPASS 39.13 seconds
TestRunner: Setup PASS 481.36 seconds
TestRunner: l2cap-tester PASS 17.23 seconds
TestRunner: bnep-tester PASS 6.08 seconds
TestRunner: mgmt-tester PASS 101.04 seconds
TestRunner: rfcomm-tester PASS 9.63 seconds
TestRunner: sco-tester PASS 9.45 seconds
TestRunner: smp-tester PASS 9.44 seconds
TestRunner: userchan-tester PASS 6.33 seconds
Details
##############################
Test: GitLint - FAIL - 1.10 seconds
Run gitlint with rule in .gitlint
Bluetooth: When HCI work queue is drained, only queue chained work.
1: T3 Title has trailing punctuation (.): "Bluetooth: When HCI work queue is drained, only queue chained work."
13: B1 Line exceeds max length (85>80): "CPU: 1 PID: 18374 Comm: kworker/1:9 Not tainted 5.18.0-rc6-next-20220516-syzkaller #0"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-05-31 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 18:41 [PATCH] Bluetooth: When HCI work queue is drained, only queue chained work Schspa Shi
2022-05-31 18:58 ` Schspa Shi
2022-05-31 19:11 ` bluez.test.bot [this message]
2022-06-02 15:37 ` Marcel Holtmann
2022-06-02 15:47 ` Schspa Shi
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=6296687e.1c69fb81.b9736.0cf2@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=schspa@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