From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, schspa@gmail.com
Subject: RE: [v2] Bluetooth: When HCI work queue is drained, only queue chained work
Date: Thu, 02 Jun 2022 12:58:52 -0700 (PDT) [thread overview]
Message-ID: <6299167c.1c69fb81.c0ec0.8c88@mx.google.com> (raw)
In-Reply-To: <20220602191949.31311-1-schspa@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1408 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=646968
---Test result---
Test Summary:
CheckPatch PASS 1.32 seconds
GitLint FAIL 0.56 seconds
SubjectPrefix PASS 0.40 seconds
BuildKernel PASS 37.80 seconds
BuildKernel32 PASS 33.80 seconds
Incremental Build with patchesPASS 45.84 seconds
TestRunner: Setup PASS 566.98 seconds
TestRunner: l2cap-tester PASS 18.27 seconds
TestRunner: bnep-tester PASS 6.34 seconds
TestRunner: mgmt-tester PASS 106.26 seconds
TestRunner: rfcomm-tester PASS 10.02 seconds
TestRunner: sco-tester PASS 9.71 seconds
TestRunner: smp-tester PASS 9.88 seconds
TestRunner: userchan-tester PASS 6.58 seconds
Details
##############################
Test: GitLint - FAIL - 0.56 seconds
Run gitlint with rule in .gitlint
[v2] Bluetooth: When HCI work queue is drained, only queue chained work
49: B1 Line exceeds max length (84>80): " - Move the workqueue drain flag to controller flags, and use hci_dev_*_flag."
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-06-02 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 19:19 [PATCH v2] Bluetooth: When HCI work queue is drained, only queue chained work Schspa Shi
2022-06-02 19:58 ` bluez.test.bot [this message]
2022-06-02 20:55 ` Luiz Augusto von Dentz
2022-06-03 8:12 ` 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=6299167c.1c69fb81.c0ec0.8c88@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