archive mirror
 help / color / mirror / Atom feed
Subject: RE: [v2] Bluetooth: hci_sync: Fix hci_update_accept_list_sync
Date: Thu, 24 Feb 2022 08:04:21 -0800 (PST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- 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:

---Test result---

Test Summary:
CheckPatch                    PASS      1.63 seconds
GitLint                       PASS      0.98 seconds
SubjectPrefix                 PASS      0.89 seconds
BuildKernel                   PASS      33.05 seconds
BuildKernel32                 PASS      29.40 seconds
Incremental Build with patchesPASS      39.56 seconds
TestRunner: Setup             PASS      514.51 seconds
TestRunner: l2cap-tester      PASS      14.40 seconds
TestRunner: bnep-tester       PASS      6.53 seconds
TestRunner: mgmt-tester       PASS      116.47 seconds
TestRunner: rfcomm-tester     PASS      9.05 seconds
TestRunner: sco-tester        PASS      8.87 seconds
TestRunner: smp-tester        PASS      8.63 seconds
TestRunner: userchan-tester   PASS      7.40 seconds

Linux Bluetooth

  reply	other threads:[~2022-02-24 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 15:11 [PATCH v2] Bluetooth: hci_sync: Fix hci_update_accept_list_sync Luiz Augusto von Dentz
2022-02-24 16:04 ` [this message]
2022-02-24 20:08 ` Marcel Holtmann
2022-05-10 10:36   ` Joey Corleone
2022-05-10 15:29     ` Thorsten Leemhuis
2022-05-16 12:40       ` [PATCH v2] Bluetooth: hci_sync: Fix hci_update_accept_list_sync #forregzbot Thorsten Leemhuis

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).