All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, tharvey@gateworks.com
Subject: RE: Bluetooth: btbcm: Add entry for BCM4373A0 UART Bluetooth
Date: Thu, 05 May 2022 14:12:13 -0700 (PDT)	[thread overview]
Message-ID: <62743dad.1c69fb81.94594.8204@mx.google.com> (raw)
In-Reply-To: <20220505195010.31329-1-tharvey@gateworks.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.58 seconds
GitLint                       PASS      0.95 seconds
SubjectPrefix                 PASS      0.90 seconds
BuildKernel                   PASS      31.53 seconds
BuildKernel32                 PASS      27.98 seconds
Incremental Build with patchesPASS      37.93 seconds
TestRunner: Setup             PASS      468.04 seconds
TestRunner: l2cap-tester      PASS      17.14 seconds
TestRunner: bnep-tester       PASS      6.10 seconds
TestRunner: mgmt-tester       PASS      101.18 seconds
TestRunner: rfcomm-tester     PASS      9.68 seconds
TestRunner: sco-tester        PASS      9.34 seconds
TestRunner: smp-tester        PASS      9.47 seconds
TestRunner: userchan-tester   PASS      6.33 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-05-05 21:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 19:50 [PATCH] Bluetooth: btbcm: Add entry for BCM4373A0 UART Bluetooth Tim Harvey
2022-05-05 21:12 ` bluez.test.bot [this message]
2022-05-13 11:21 ` 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=62743dad.1c69fb81.94594.8204@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=tharvey@gateworks.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.