From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, mmandlik@google.com
Subject: RE: Add Advertisement Monitor Device Found/Lost events
Date: Mon, 25 Oct 2021 12:56:29 -0700 (PDT) [thread overview]
Message-ID: <61770bed.1c69fb81.de7a4.f25b@mx.google.com> (raw)
In-Reply-To: <20211025121343.BlueZ.v4.1.I7f6bdb9282c1e12ffc6c662674678f2b1cb69182@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=569881
---Test result---
Test Summary:
CheckPatch PASS 4.39 seconds
GitLint PASS 2.90 seconds
Prep - Setup ELL PASS 52.11 seconds
Build - Prep PASS 0.54 seconds
Build - Configure PASS 9.39 seconds
Build - Make PASS 225.67 seconds
Make Check PASS 9.84 seconds
Make Distcheck PASS 266.48 seconds
Build w/ext ELL - Configure PASS 9.65 seconds
Build w/ext ELL - Make PASS 214.45 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2021-10-25 20:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 19:18 [BlueZ PATCH v4 0/3] Add Advertisement Monitor Device Found/Lost events Manish Mandlik
2021-10-25 19:18 ` [BlueZ PATCH v4 1/3] doc: Introduce the Adv " Manish Mandlik
2021-10-25 19:56 ` bluez.test.bot [this message]
2021-10-25 20:03 ` Marcel Holtmann
[not found] ` <CAGPPCLBNN+Eg92=GnmbMBfngLEb=BL6sSkx7O19rYOydAkO8HA@mail.gmail.com>
2021-10-26 8:33 ` Marcel Holtmann
[not found] ` <CAGPPCLD+pYQtK8G303gr_F7xqTvuSXA+4FTRiVf0OzAEUrDgjw@mail.gmail.com>
2021-11-08 22:57 ` Luiz Augusto von Dentz
[not found] ` <CAGPPCLBAwp=64hysCeagLQDrwK5b7_nUGS73XB0eDgsGL7yAsQ@mail.gmail.com>
2021-11-09 6:31 ` Luiz Augusto von Dentz
2021-10-25 19:18 ` [BlueZ PATCH v4 2/3] lib: Add definitions of " Manish Mandlik
2021-10-25 19:18 ` [BlueZ PATCH v4 3/3] adv_monitor: Receive the " Manish Mandlik
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=61770bed.1c69fb81.de7a4.f25b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mmandlik@google.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.