All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hj.tedd.an@gmail.com
Subject: RE: [BlueZ,v2] tools/ioctl-tester - Add ioctl-tester
Date: Wed, 21 Sep 2022 13:24:31 -0700 (PDT)	[thread overview]
Message-ID: <632b72ff.050a0220.7a43a.af9a@mx.google.com> (raw)
In-Reply-To: <20220921192826.102801-1-hj.tedd.an@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      2.44 seconds
GitLint                       PASS      1.13 seconds
Prep - Setup ELL              PASS      27.93 seconds
Build - Prep                  PASS      0.87 seconds
Build - Configure             PASS      8.91 seconds
Build - Make                  PASS      1001.77 seconds
Make Check                    PASS      12.25 seconds
Make Check w/Valgrind         PASS      296.65 seconds
Make Distcheck                PASS      247.77 seconds
Build w/ext ELL - Configure   PASS      8.94 seconds
Build w/ext ELL - Make        PASS      86.63 seconds
Incremental Build w/ patches  PASS      0.00 seconds
Scan Build                    PASS      577.90 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-09-21 20:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 19:28 [BlueZ PATCH v2] tools/ioctl-tester - Add ioctl-tester Tedd Ho-Jeong An
2022-09-21 20:24 ` bluez.test.bot [this message]
2022-09-22  1:10 ` 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=632b72ff.050a0220.7a43a.af9a@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=hj.tedd.an@gmail.com \
    --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 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.