From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, apusaka@google.com
Subject: RE: Bluetooth: hci_sync: cancel cmd_timer if hci_open failed
Date: Wed, 05 Oct 2022 00:35:14 -0700 (PDT) [thread overview]
Message-ID: <633d33b2.020a0220.568a4.2915@mx.google.com> (raw)
In-Reply-To: <20221005150934.1.Ife932473db2eec6f0bc54226c3328e5fa8c5f97b@changeid>
[-- Attachment #1: Type: text/plain, Size: 1206 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=683158
---Test result---
Test Summary:
CheckPatch PASS 2.38 seconds
GitLint PASS 0.79 seconds
SubjectPrefix PASS 0.69 seconds
BuildKernel PASS 49.88 seconds
BuildKernel32 PASS 41.45 seconds
Incremental Build with patchesPASS 54.45 seconds
TestRunner: Setup PASS 731.82 seconds
TestRunner: l2cap-tester PASS 17.16 seconds
TestRunner: iso-tester PASS 16.55 seconds
TestRunner: bnep-tester PASS 6.21 seconds
TestRunner: mgmt-tester PASS 106.64 seconds
TestRunner: rfcomm-tester PASS 10.10 seconds
TestRunner: sco-tester PASS 9.29 seconds
TestRunner: ioctl-tester PASS 10.61 seconds
TestRunner: smp-tester PASS 9.48 seconds
TestRunner: userchan-tester PASS 6.49 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-10-05 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 7:09 [PATCH] Bluetooth: hci_sync: cancel cmd_timer if hci_open failed Archie Pusaka
2022-10-05 7:35 ` bluez.test.bot [this message]
2022-10-11 19:40 ` patchwork-bot+bluetooth
2023-01-26 13:36 [PATCH 6.1 1/1] " Fedor Pchelkin
2023-01-26 13:43 ` 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=633d33b2.020a0220.568a4.2915@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=apusaka@google.com \
--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).