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, luiz.dentz@gmail.com
Subject: RE: Bluetooth: Add CONFIG_BT_LE_L2CAP_ECRED
Date: Thu, 27 Oct 2022 17:12:19 -0700 (PDT)	[thread overview]
Message-ID: <635b1e63.c80a0220.41d1f.6e7f@mx.google.com> (raw)
In-Reply-To: <20221027232528.1996093-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.83 seconds
GitLint                       PASS      1.05 seconds
SubjectPrefix                 PASS      0.88 seconds
BuildKernel                   PASS      34.27 seconds
BuildKernel32                 PASS      31.02 seconds
Incremental Build with patchesPASS      46.58 seconds
TestRunner: Setup             PASS      514.95 seconds
TestRunner: l2cap-tester      PASS      17.48 seconds
TestRunner: iso-tester        PASS      16.75 seconds
TestRunner: bnep-tester       PASS      6.64 seconds
TestRunner: mgmt-tester       PASS      106.88 seconds
TestRunner: rfcomm-tester     PASS      10.50 seconds
TestRunner: sco-tester        PASS      9.95 seconds
TestRunner: ioctl-tester      PASS      11.37 seconds
TestRunner: mesh-tester       PASS      8.19 seconds
TestRunner: smp-tester        PASS      10.02 seconds
TestRunner: userchan-tester   PASS      6.99 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-10-28  0:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27 23:25 [PATCH] Bluetooth: Add CONFIG_BT_LE_L2CAP_ECRED Luiz Augusto von Dentz
2022-10-28  0:12 ` bluez.test.bot [this message]
2022-10-28 23: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=635b1e63.c80a0220.41d1f.6e7f@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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