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: Tue, 07 Jun 2022 04:04:47 -0700 (PDT) [thread overview]
Message-ID: <629f30cf.1c69fb81.f8003.1167@mx.google.com> (raw)
In-Reply-To: <20220607104015.2126118-1-poprdi@google.com>
[-- Attachment #1: Type: text/plain, Size: 1097 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=647954
---Test result---
Test Summary:
CheckPatch PASS 1.24 seconds
GitLint PASS 0.84 seconds
SubjectPrefix PASS 0.62 seconds
BuildKernel PASS 30.66 seconds
BuildKernel32 PASS 27.33 seconds
Incremental Build with patchesPASS 37.37 seconds
TestRunner: Setup PASS 467.41 seconds
TestRunner: l2cap-tester PASS 17.70 seconds
TestRunner: bnep-tester PASS 5.98 seconds
TestRunner: mgmt-tester PASS 100.14 seconds
TestRunner: rfcomm-tester PASS 9.56 seconds
TestRunner: sco-tester PASS 9.27 seconds
TestRunner: smp-tester PASS 9.32 seconds
TestRunner: userchan-tester PASS 6.25 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-06-07 11:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 10:40 [PATCH v2] Bluetooth: Collect kcov coverage from hci_rx_work Tamas Koczka
2022-06-07 11:04 ` bluez.test.bot [this message]
2022-06-07 11:44 ` Tamás Koczka
2022-06-14 13:34 ` Tamás Koczka
2022-06-22 10:20 ` Aleksandr Nogikh
2022-06-23 9:18 ` Dmitry Vyukov
2022-07-04 12:52 ` Tamás Koczka
-- strict thread matches above, loose matches on Subject: below --
2022-07-14 10:48 Tamas Koczka
2022-07-14 11:55 ` [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=629f30cf.1c69fb81.f8003.1167@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 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.