linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, jiangzp@google.com
Subject: RE: Bluetooth: hci_sync: Fix resuming scan after suspend resume
Date: Mon, 11 Jul 2022 20:17:36 -0700 (PDT)	[thread overview]
Message-ID: <62cce7d0.1c69fb81.7ac83.27a2@mx.google.com> (raw)
In-Reply-To: <20220711170515.kernel.v2.1.Ia489394ab4176efa5a39ce8d08bb4c4b7bee23b9@changeid>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.60 seconds
GitLint                       PASS      0.77 seconds
SubjectPrefix                 PASS      0.71 seconds
BuildKernel                   PASS      31.65 seconds
BuildKernel32                 PASS      26.96 seconds
Incremental Build with patchesPASS      37.72 seconds
TestRunner: Setup             PASS      463.20 seconds
TestRunner: l2cap-tester      PASS      16.32 seconds
TestRunner: bnep-tester       PASS      5.49 seconds
TestRunner: mgmt-tester       PASS      94.37 seconds
TestRunner: rfcomm-tester     PASS      8.93 seconds
TestRunner: sco-tester        PASS      8.69 seconds
TestRunner: smp-tester        PASS      8.72 seconds
TestRunner: userchan-tester   PASS      5.69 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-07-12  3:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12  0:05 [kernel PATCH v2 0/1] Bluetooth: hci_sync: Fix resuming scan after suspend resume Zhengping Jiang
2022-07-12  0:05 ` [kernel PATCH v2 1/1] " Zhengping Jiang
2022-07-12  3:17   ` bluez.test.bot [this message]
2022-07-12 20:10 ` [kernel PATCH v2 0/1] " patchwork-bot+bluetooth

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=62cce7d0.1c69fb81.7ac83.27a2@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=jiangzp@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;
as well as URLs for NNTP newsgroup(s).