linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ] build: Check for linux/uinput.h and linux/uhid.h
Date: Tue, 23 Nov 2021 13:54:26 -0800 (PST)	[thread overview]
Message-ID: <619d6312.1c69fb81.7a59.37dc@mx.google.com> (raw)
In-Reply-To: <20211123213450.2595964-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.38 seconds
GitLint                       PASS      0.93 seconds
Prep - Setup ELL              PASS      42.36 seconds
Build - Prep                  PASS      0.48 seconds
Build - Configure             PASS      8.05 seconds
Build - Make                  PASS      179.89 seconds
Make Check                    PASS      9.19 seconds
Make Distcheck                PASS      214.98 seconds
Build w/ext ELL - Configure   PASS      8.16 seconds
Build w/ext ELL - Make        PASS      171.20 seconds



---
Regards,
Linux Bluetooth


      reply	other threads:[~2021-11-23 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 21:34 [PATCH BlueZ] build: Check for linux/uinput.h and linux/uhid.h Luiz Augusto von Dentz
2021-11-23 21:54 ` bluez.test.bot [this message]

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=619d6312.1c69fb81.7a59.37dc@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;
as well as URLs for NNTP newsgroup(s).