From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, simon.mikuda@streamunlimited.com
Subject: RE: Adapter1.ConnectDevice
Date: Thu, 27 Jul 2023 23:33:30 -0700 (PDT) [thread overview]
Message-ID: <64c3613a.020a0220.f7f2b.19e1@mx.google.com> (raw)
In-Reply-To: <20230728052506.582394-2-simon.mikuda@streamunlimited.com>
[-- Attachment #1: Type: text/plain, Size: 947 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=770400
---Test result---
Test Summary:
CheckPatch PASS 0.38 seconds
GitLint PASS 0.29 seconds
BuildEll PASS 27.01 seconds
BluezMake PASS 793.15 seconds
MakeCheck PASS 12.10 seconds
MakeDistcheck PASS 159.63 seconds
CheckValgrind PASS 252.47 seconds
CheckSmatch PASS 338.10 seconds
bluezmakeextell PASS 102.34 seconds
IncrementalBuild PASS 657.82 seconds
ScanBuild PASS 1022.18 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-07-28 6:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 5:25 [PATCH BlueZ 0/1] Adapter1.ConnectDevice Simon Mikuda
2023-07-28 5:25 ` [PATCH BlueZ 1/1] adapter: Be able to use ConnectDevice for discovered devices Simon Mikuda
2023-07-28 6:33 ` bluez.test.bot [this message]
2023-07-28 17:48 ` Luiz Augusto von Dentz
2023-07-31 4:12 ` [PATCH BlueZ 1/2] " Simon Mikuda
2023-07-31 4:12 ` [PATCH BlueZ 2/2] adapter: Update ConnectDevice documentation Simon Mikuda
2023-07-31 5:43 ` [PATCH BlueZ 1/2] adapter: Be able to use ConnectDevice for discovered devices Paul Menzel
2023-07-31 6:24 ` Simon Mikuda
2023-07-31 6:04 ` [BlueZ,1/2] " bluez.test.bot
2023-07-31 17:50 ` [PATCH BlueZ 1/2] " patchwork-bot+bluetooth
2023-07-28 17:44 ` [PATCH BlueZ 0/1] Adapter1.ConnectDevice Luiz Augusto von Dentz
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=64c3613a.020a0220.f7f2b.19e1@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=simon.mikuda@streamunlimited.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.