From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, mmandlik@google.com
Subject: RE: [BlueZ,v5,1/6] doc: Introduce the Adv Monitor Device Found/Lost events
Date: Wed, 17 Nov 2021 11:32:02 -0800 (PST) [thread overview]
Message-ID: <619558b2.1c69fb81.b55fd.1e93@mx.google.com> (raw)
In-Reply-To: <20211117110627.BlueZ.v5.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=581841
---Test result---
Test Summary:
CheckPatch PASS 2.89 seconds
GitLint PASS 1.83 seconds
Prep - Setup ELL PASS 43.79 seconds
Build - Prep PASS 0.23 seconds
Build - Configure PASS 8.02 seconds
Build - Make PASS 192.03 seconds
Make Check PASS 9.33 seconds
Make Distcheck PASS 227.33 seconds
Build w/ext ELL - Configure PASS 8.32 seconds
Build w/ext ELL - Make PASS 181.16 seconds
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2021-11-17 19:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 19:14 [BlueZ PATCH v5 1/6] doc: Introduce the Adv Monitor Device Found/Lost events Manish Mandlik
2021-11-17 19:14 ` [BlueZ PATCH v5 2/6] lib: Add definitions of " Manish Mandlik
2021-11-17 19:14 ` [BlueZ PATCH v5 3/6] adv_monitor: Receive the " Manish Mandlik
2021-11-17 21:42 ` Luiz Augusto von Dentz
2021-11-17 19:14 ` [BlueZ PATCH v5 4/6] adv_monitor: Invoke DeviceFound/Lost on tracked monitors Manish Mandlik
2021-11-17 19:14 ` [BlueZ PATCH v5 5/6] adv_monitor: Change sampling period to uint16_t Manish Mandlik
2021-11-17 19:14 ` [BlueZ PATCH v5 6/6] core: Update default advmon Sampling_Period to 0xFF Manish Mandlik
2021-11-17 21:09 ` Luiz Augusto von Dentz
[not found] ` <CAGPPCLB9KSDG1LFYeeKnPjtD001Q00PXgkRnh8Xz_9N=zB+mqg@mail.gmail.com>
2021-11-19 19:40 ` Luiz Augusto von Dentz
2021-11-17 19:32 ` bluez.test.bot [this message]
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=619558b2.1c69fb81.b55fd.1e93@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).