linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: Shyh-In Hwang <josephsih@chromium.org>
Subject: Re: [BlueZ,v6,1/3] monitor: add new Intel extended telemetry events
Date: Tue, 20 Jul 2021 11:06:59 -0700	[thread overview]
Message-ID: <CABBYNZL+gxxHVUGK_74Gh56Z=RK68r=L2ZRF=1w2+0ROwi52dQ@mail.gmail.com> (raw)
In-Reply-To: <60f010bf.1c69fb81.6775f.4720@mx.google.com>

Hi Joseph,

On Thu, Jul 15, 2021 at 5:07 AM <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=516039
>
> ---Test result---
>
> Test Summary:
> CheckPatch                    PASS      1.31 seconds
> GitLint                       PASS      0.37 seconds
> Prep - Setup ELL              PASS      47.86 seconds
> Build - Prep                  PASS      0.14 seconds
> Build - Configure             PASS      8.22 seconds
> Build - Make                  PASS      211.38 seconds
> Make Check                    PASS      9.48 seconds
> Make Distcheck                PASS      249.82 seconds
> Build w/ext ELL - Configure   PASS      8.57 seconds
> Build w/ext ELL - Make        PASS      206.23 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. Note that I did change the command name for exp-bqr
to exp-quality to make it more clear what is doing from the command
name itself.

-- 
Luiz Augusto von Dentz

      reply	other threads:[~2021-07-20 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15  9:50 [BlueZ PATCH v6 1/3] monitor: add new Intel extended telemetry events Joseph Hwang
2021-07-15  9:50 ` [BlueZ PATCH v6 2/3] adapter: read quality report feature Joseph Hwang
2021-07-15  9:50 ` [BlueZ PATCH v6 3/3] tools: btmgmt: support bqr experiment feature command Joseph Hwang
2021-07-15 10:41 ` [BlueZ,v6,1/3] monitor: add new Intel extended telemetry events bluez.test.bot
2021-07-20 18:06   ` 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='CABBYNZL+gxxHVUGK_74Gh56Z=RK68r=L2ZRF=1w2+0ROwi52dQ@mail.gmail.com' \
    --to=luiz.dentz@gmail.com \
    --cc=josephsih@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 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).