From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, apusaka@google.com
Subject: RE: [Bluez,1/3] adapter: Use PeripheralLongTermKey to store LTK
Date: Sun, 31 Oct 2021 23:41:54 -0700 (PDT) [thread overview]
Message-ID: <617f8c32.1c69fb81.8d919.e570@mx.google.com> (raw)
In-Reply-To: <20211101140544.Bluez.1.I515833d2764b8ec2ac2bb1f87313de80ebb497cd@changeid>
[-- Attachment #1: Type: text/plain, Size: 884 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=573377
---Test result---
Test Summary:
CheckPatch PASS 4.10 seconds
GitLint PASS 2.80 seconds
Prep - Setup ELL PASS 42.57 seconds
Build - Prep PASS 0.50 seconds
Build - Configure PASS 7.91 seconds
Build - Make PASS 182.22 seconds
Make Check PASS 9.23 seconds
Make Distcheck PASS 218.49 seconds
Build w/ext ELL - Configure PASS 8.01 seconds
Build w/ext ELL - Make PASS 173.06 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2021-11-01 6:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 6:06 [Bluez PATCH 1/3] adapter: Use PeripheralLongTermKey to store LTK Archie Pusaka
2021-11-01 6:06 ` [Bluez PATCH 2/3] doc: Add PeripheralLongTermKey for storing LTK Archie Pusaka
2021-11-01 6:06 ` [Bluez PATCH 3/3] adapter: Remove "Master" entry from LTK storage Archie Pusaka
2021-11-02 6:13 ` Luiz Augusto von Dentz
2021-11-02 9:17 ` Archie Pusaka
2021-11-01 6:41 ` bluez.test.bot [this message]
2021-11-02 6:17 ` [Bluez PATCH 1/3] adapter: Use PeripheralLongTermKey to store LTK Luiz Augusto von Dentz
2021-11-02 9:10 ` Archie Pusaka
2021-11-02 22:39 ` 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=617f8c32.1c69fb81.8d919.e570@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