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, Larry.Finger@lwfinger.net
Subject: RE: [v2,1/2] Bluetooth: Add device 0bda:887b to device tables
Date: Thu, 23 Mar 2023 11:35:24 -0700 (PDT)	[thread overview]
Message-ID: <641c9bec.370a0220.3b5c0.0494@mx.google.com> (raw)
In-Reply-To: <20230323174604.30088-1-Larry.Finger@lwfinger.net>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.68 seconds
GitLint                       PASS      0.34 seconds
SubjectPrefix                 PASS      0.13 seconds
BuildKernel                   PASS      31.05 seconds
CheckAllWarning               PASS      33.89 seconds
CheckSparse                   PASS      39.06 seconds
CheckSmatch                   PASS      107.90 seconds
BuildKernel32                 PASS      30.11 seconds
TestRunnerSetup               PASS      433.85 seconds
TestRunner_l2cap-tester       PASS      15.89 seconds
TestRunner_iso-tester         PASS      15.60 seconds
TestRunner_bnep-tester        PASS      5.15 seconds
TestRunner_mgmt-tester        PASS      102.76 seconds
TestRunner_rfcomm-tester      PASS      8.21 seconds
TestRunner_sco-tester         PASS      7.59 seconds
TestRunner_ioctl-tester       PASS      8.68 seconds
TestRunner_mesh-tester        PASS      6.49 seconds
TestRunner_smp-tester         PASS      7.46 seconds
TestRunner_userchan-tester    PASS      5.39 seconds
IncrementalBuild              PASS      28.31 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-03-23 18:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23  0:52 [PATCH 0/2] Bluetooth: Two additional devices Larry Finger
2023-03-23  0:52 ` [PATCH 1/2] bluetooth: Add device 0bda:887b to device tables Larry Finger
2023-03-23  2:30   ` Bluetooth: Two additional devices bluez.test.bot
2023-03-23  0:52 ` [PATCH 2/2] bluetooth: Add device 13d3:3571 to device tables Larry Finger
2023-03-23 17:45 ` [PATCH v2 0/2] Bluetooth: Two additional devices Larry Finger
2023-03-23 17:45 ` [PATCH v2 1/2] Bluetooth: Add device 0bda:887b to device tables Larry Finger
2023-03-23 18:35   ` bluez.test.bot [this message]
2023-03-28 21:00   ` patchwork-bot+bluetooth
2023-03-23 17:45 ` [PATCH 2/2] Bluetooth: Add device 13d3:3571 " Larry Finger
2023-03-23 18:16   ` [2/2] " bluez.test.bot
2023-03-28 21:00   ` [PATCH 2/2] " patchwork-bot+bluetooth
2023-03-28 21:00 ` [PATCH 0/2] Bluetooth: Two additional devices 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=641c9bec.370a0220.3b5c0.0494@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --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