All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/2] bthost: Fix not setting all parameters when using Create BIG cmd
Date: Fri, 11 Mar 2022 17:24:28 -0800 (PST)	[thread overview]
Message-ID: <622bf64c.1c69fb81.9fb3a.bce8@mx.google.com> (raw)
In-Reply-To: <20220311211730.3285028-1-luiz.dentz@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1000 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=622790

---Test result---

Test Summary:
CheckPatch                    PASS      3.05 seconds
GitLint                       PASS      2.12 seconds
Prep - Setup ELL              PASS      55.50 seconds
Build - Prep                  PASS      0.88 seconds
Build - Configure             PASS      11.01 seconds
Build - Make                  PASS      1549.91 seconds
Make Check                    PASS      12.81 seconds
Make Check w/Valgrind         PASS      566.40 seconds
Make Distcheck                PASS      295.67 seconds
Build w/ext ELL - Configure   PASS      11.28 seconds
Build w/ext ELL - Make        PASS      1520.49 seconds
Incremental Build with patchesPASS      3122.33 seconds



---
Regards,
Linux Bluetooth


      parent reply	other threads:[~2022-03-12  1:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 21:17 [PATCH BlueZ 1/2] bthost: Fix not setting all parameters when using Create BIG cmd Luiz Augusto von Dentz
2022-03-11 21:17 ` [PATCH BlueZ 2/2] btdev: Fix CIS Established Luiz Augusto von Dentz
2022-03-12  1:24 ` 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=622bf64c.1c69fb81.9fb3a.bce8@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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.