From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, poprdi@google.com
Subject: RE: [v2] Bluetooth: Collect kcov coverage from hci_rx_work
Date: Thu, 14 Jul 2022 04:55:51 -0700 (PDT) [thread overview]
Message-ID: <62d00447.1c69fb81.d74df.0795@mx.google.com> (raw)
In-Reply-To: <20220714104814.1296858-1-poprdi@google.com>
[-- Attachment #1: Type: text/plain, Size: 1438 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=659660
---Test result---
Test Summary:
CheckPatch PASS 1.26 seconds
GitLint FAIL 0.56 seconds
SubjectPrefix PASS 0.39 seconds
BuildKernel PASS 31.70 seconds
BuildKernel32 PASS 27.34 seconds
Incremental Build with patchesPASS 37.80 seconds
TestRunner: Setup PASS 468.97 seconds
TestRunner: l2cap-tester PASS 16.30 seconds
TestRunner: bnep-tester PASS 5.46 seconds
TestRunner: mgmt-tester PASS 95.42 seconds
TestRunner: rfcomm-tester PASS 8.90 seconds
TestRunner: sco-tester PASS 8.60 seconds
TestRunner: smp-tester PASS 8.65 seconds
TestRunner: userchan-tester PASS 5.65 seconds
Details
##############################
Test: GitLint - FAIL - 0.56 seconds
Run gitlint with rule in .gitlint
[v2] Bluetooth: Collect kcov coverage from hci_rx_work
24: B1 Line exceeds max length (132>80): "Note: this is a resubmission of https://lore.kernel.org/netdev/CAPUC6bJbVMPn1FMLYnXg2GUX4ikesMSRjj=oPOOrS5H2DOx_bA@mail.gmail.com/T/"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-07-14 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 10:48 [PATCH v2] Bluetooth: Collect kcov coverage from hci_rx_work Tamas Koczka
2022-07-14 11:55 ` bluez.test.bot [this message]
2022-07-14 20:00 ` patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2022-06-07 10:40 Tamas Koczka
2022-06-07 11:04 ` [v2] " bluez.test.bot
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=62d00447.1c69fb81.d74df.0795@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=poprdi@google.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;
as well as URLs for NNTP newsgroup(s).