public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, apusaka@google.com
Subject: RE: [Bluez,v2] device: Fix device can't be scanned for 5 mins after reboot
Date: Thu, 13 Jan 2022 01:30:49 -0800 (PST)	[thread overview]
Message-ID: <61dff149.1c69fb81.415f4.8d3e@mx.google.com> (raw)
In-Reply-To: <20220113154626.Bluez.v2.1.Iad485a29772515142eefb1b120d5eb5e101d82f6@changeid>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.44 seconds
GitLint                       PASS      0.97 seconds
Prep - Setup ELL              PASS      42.40 seconds
Build - Prep                  PASS      0.70 seconds
Build - Configure             PASS      8.52 seconds
Build - Make                  PASS      1403.75 seconds
Make Check                    PASS      12.08 seconds
Make Check w/Valgrind         PASS      437.97 seconds
Make Distcheck                PASS      232.37 seconds
Build w/ext ELL - Configure   PASS      8.66 seconds
Build w/ext ELL - Make        PASS      1365.55 seconds
Incremental Build with patchesPASS      0.00 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-01-13  9:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13  7:46 [Bluez PATCH v2] device: Fix device can't be scanned for 5 mins after reboot Archie Pusaka
2022-01-13  9:30 ` bluez.test.bot [this message]
2022-01-13 21:36   ` [Bluez,v2] " Luiz Augusto von Dentz

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=61dff149.1c69fb81.415f4.8d3e@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=apusaka@google.com \
    --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