From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, clancy_shang@163.com
Subject: RE: [BlueZ] adapter: Fix execute "LE Add Device To Resolving List" command fail
Date: Sun, 04 Aug 2024 20:50:48 -0700 (PDT) [thread overview]
Message-ID: <66b04c18.170a0220.d077e.f5c0@mx.google.com> (raw)
In-Reply-To: <20240805020126.903959-1-clancy_shang@163.com>
[-- Attachment #1: Type: text/plain, Size: 948 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=876563
---Test result---
Test Summary:
CheckPatch PASS 0.53 seconds
GitLint PASS 0.39 seconds
BuildEll PASS 24.58 seconds
BluezMake PASS 1690.32 seconds
MakeCheck PASS 12.79 seconds
MakeDistcheck PASS 177.38 seconds
CheckValgrind PASS 253.01 seconds
CheckSmatch PASS 355.96 seconds
bluezmakeextell PASS 121.27 seconds
IncrementalBuild PASS 1461.63 seconds
ScanBuild PASS 998.60 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-08-05 3:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 2:01 [PATCH] [BlueZ] adapter: Fix execute "LE Add Device To Resolving List" command fail clancy_shang
2024-08-05 3:50 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-21 1:35 clancy_shang
2024-08-21 3:51 ` bluez.test.bot
2024-07-31 1:57 [PATCH] " clancy_shang
2024-07-31 3:33 ` bluez.test.bot
2024-07-22 7:56 [PATCH] " clancy_shang
2024-07-22 9:38 ` bluez.test.bot
2024-07-22 6:02 [PATCH] " clancy_shang
2024-07-22 7:39 ` bluez.test.bot
2024-07-22 5:27 [PATCH] " clancy_shang
2024-07-22 5:38 ` bluez.test.bot
2024-07-22 2:27 [PATCH] " clancy_shang
2024-07-22 4:05 ` 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=66b04c18.170a0220.d077e.f5c0@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=clancy_shang@163.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 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.