From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, jiangzp@google.com
Subject: RE: Fix refresh cached connection info
Date: Mon, 13 Jun 2022 16:04:07 -0700 (PDT) [thread overview]
Message-ID: <62a7c267.1c69fb81.47545.6fbd@mx.google.com> (raw)
In-Reply-To: <20220613144322.kernel.v1.1.Ia621daca5b03278ee09314c59659b64c901408cf@changeid>
[-- Attachment #1: Type: text/plain, Size: 1100 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=649987
---Test result---
Test Summary:
CheckPatch PASS 0.86 seconds
GitLint PASS 0.46 seconds
SubjectPrefix PASS 0.30 seconds
BuildKernel PASS 38.53 seconds
BuildKernel32 PASS 34.31 seconds
Incremental Build with patchesPASS 45.95 seconds
TestRunner: Setup PASS 572.80 seconds
TestRunner: l2cap-tester PASS 19.34 seconds
TestRunner: bnep-tester PASS 6.96 seconds
TestRunner: mgmt-tester PASS 116.57 seconds
TestRunner: rfcomm-tester PASS 10.94 seconds
TestRunner: sco-tester PASS 10.47 seconds
TestRunner: smp-tester PASS 10.43 seconds
TestRunner: userchan-tester PASS 7.09 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-06-13 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 21:43 [kernel PATCH v1 0/1] Fix refresh cached connection info Zhengping Jiang
2022-06-13 21:43 ` [kernel PATCH v1 1/1] Bluetooth: mgmt: " Zhengping Jiang
2022-06-13 23:04 ` bluez.test.bot [this message]
2022-06-21 19:30 ` [kernel PATCH v1 0/1] " patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2022-06-10 19:19 [kernel PATCH v1 1/1] Bluetooth: mgmt: " Zhengping Jiang
2022-06-10 19:55 ` 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=62a7c267.1c69fb81.47545.6fbd@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=jiangzp@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).