linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_zijuhu@quicinc.com
Subject: RE: [v1] Bluetooth: hci_sync: Correct hci_set_event_mask_page_2_sync() event mask
Date: Wed, 13 Jul 2022 00:56:26 -0700 (PDT)	[thread overview]
Message-ID: <62ce7aaa.1c69fb81.f47d7.58a8@mx.google.com> (raw)
In-Reply-To: <1657695194-25801-1-git-send-email-quic_zijuhu@quicinc.com>

[-- 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=659174

---Test result---

Test Summary:
CheckPatch                    PASS      1.85 seconds
GitLint                       PASS      0.94 seconds
SubjectPrefix                 PASS      0.82 seconds
BuildKernel                   PASS      29.89 seconds
BuildKernel32                 PASS      25.76 seconds
Incremental Build with patchesPASS      35.02 seconds
TestRunner: Setup             PASS      429.54 seconds
TestRunner: l2cap-tester      PASS      16.44 seconds
TestRunner: bnep-tester       PASS      5.55 seconds
TestRunner: mgmt-tester       PASS      90.61 seconds
TestRunner: rfcomm-tester     PASS      8.67 seconds
TestRunner: sco-tester        PASS      8.44 seconds
TestRunner: smp-tester        PASS      8.60 seconds
TestRunner: userchan-tester   PASS      5.68 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-07-13  7:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13  6:53 [PATCH v1] Bluetooth: hci_sync: Correct hci_set_event_mask_page_2_sync() event mask Zijun Hu
2022-07-13  7:56 ` bluez.test.bot [this message]
2022-07-20 16:50 ` 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=62ce7aaa.1c69fb81.f47d7.58a8@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=quic_zijuhu@quicinc.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 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).