From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: Alain Michaud <alainm@chromium.org>
Subject: Re: [Bluez,v2] monitor: Adding missing device found flag in the parser
Date: Wed, 16 Jun 2021 15:44:09 -0700 [thread overview]
Message-ID: <CABBYNZ+Qhs4aMzr48LJndDCdqDUp36K_jQJuucqTMQU9442UEQ@mail.gmail.com> (raw)
In-Reply-To: <60ca00cc.1c69fb81.e64fd.6a86@mx.google.com>
Hi Alain,
On Wed, Jun 16, 2021 at 12:53 PM <bluez.test.bot@gmail.com> wrote:
>
> 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=501559
>
> ---Test result---
>
> Test Summary:
> CheckPatch PASS 0.70 seconds
> GitLint PASS 0.09 seconds
> Prep - Setup ELL PASS 38.67 seconds
> Build - Prep PASS 0.09 seconds
> Build - Configure PASS 6.50 seconds
> Build - Make PASS 161.00 seconds
> Make Check PASS 8.75 seconds
> Make Distcheck PASS 189.81 seconds
> Build w/ext ELL - Configure PASS 6.51 seconds
> Build w/ext ELL - Make PASS 150.88 seconds
>
> Details
> ##############################
> Test: CheckPatch - PASS
> Desc: Run checkpatch.pl script with rule in .checkpatch.conf
>
> ##############################
> Test: GitLint - PASS
> Desc: Run gitlint with rule in .gitlint
>
> ##############################
> Test: Prep - Setup ELL - PASS
> Desc: Clone, build, and install ELL
>
> ##############################
> Test: Build - Prep - PASS
> Desc: Prepare environment for build
>
> ##############################
> Test: Build - Configure - PASS
> Desc: Configure the BlueZ source tree
>
> ##############################
> Test: Build - Make - PASS
> Desc: Build the BlueZ source tree
>
> ##############################
> Test: Make Check - PASS
> Desc: Run 'make check'
>
> ##############################
> Test: Make Distcheck - PASS
> Desc: Run distcheck to check the distribution
>
> ##############################
> Test: Build w/ext ELL - Configure - PASS
> Desc: Configure BlueZ source with '--enable-external-ell' configuration
>
> ##############################
> Test: Build w/ext ELL - Make - PASS
> Desc: Build BlueZ source with '--enable-external-ell' configuration
>
>
>
> ---
> Regards,
> Linux Bluetooth
Applied, thanks.
--
Luiz Augusto von Dentz
prev parent reply other threads:[~2021-06-16 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 12:42 [Bluez PATCH v2] monitor: Adding missing device found flag in the parser Alain Michaud
2021-06-16 13:46 ` [Bluez,v2] " bluez.test.bot
2021-06-16 22:44 ` Luiz Augusto von Dentz [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=CABBYNZ+Qhs4aMzr48LJndDCdqDUp36K_jQJuucqTMQU9442UEQ@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=alainm@chromium.org \
--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.