public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, apusaka@google.com
Subject: RE: [Bluez,v2,1/3] adapter: Use PeripheralLongTermKey to store LTK
Date: Wed, 03 Nov 2021 02:38:25 -0700 (PDT)	[thread overview]
Message-ID: <61825891.1c69fb81.61efa.6759@mx.google.com> (raw)
In-Reply-To: <20211103170206.Bluez.v2.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=574639

---Test result---

Test Summary:
CheckPatch                    PASS      4.46 seconds
GitLint                       PASS      3.02 seconds
Prep - Setup ELL              PASS      49.79 seconds
Build - Prep                  PASS      0.54 seconds
Build - Configure             PASS      9.54 seconds
Build - Make                  PASS      216.71 seconds
Make Check                    PASS      9.87 seconds
Make Distcheck                PASS      251.91 seconds
Build w/ext ELL - Configure   PASS      8.81 seconds
Build w/ext ELL - Make        PASS      198.37 seconds



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2021-11-03  9:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03  9:02 [Bluez PATCH v2 1/3] adapter: Use PeripheralLongTermKey to store LTK Archie Pusaka
2021-11-03  9:02 ` [Bluez PATCH v2 2/3] doc: Add PeripheralLongTermKey for storing LTK Archie Pusaka
2021-11-03  9:02 ` [Bluez PATCH v2 3/3] adapter: Remove "Master" entry from LTK storage Archie Pusaka
2021-11-03  9:38 ` bluez.test.bot [this message]
2021-11-04  0:39   ` [Bluez,v2,1/3] adapter: Use PeripheralLongTermKey to store LTK 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=61825891.1c69fb81.61efa.6759@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