From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v2,1/2] hog-lib: Don't restrict Report MAP size
Date: Tue, 16 Aug 2022 16:13:52 -0700 (PDT) [thread overview]
Message-ID: <62fc24b0.a70a0220.b7101.ef6f@mx.google.com> (raw)
In-Reply-To: <20220816220548.1555673-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1051 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=668224
---Test result---
Test Summary:
CheckPatch PASS 1.39 seconds
GitLint PASS 0.92 seconds
Prep - Setup ELL PASS 32.69 seconds
Build - Prep PASS 0.70 seconds
Build - Configure PASS 10.39 seconds
Build - Make PASS 991.54 seconds
Make Check PASS 12.29 seconds
Make Check w/Valgrind PASS 345.94 seconds
Make Distcheck PASS 295.42 seconds
Build w/ext ELL - Configure PASS 10.63 seconds
Build w/ext ELL - Make PASS 98.58 seconds
Incremental Build w/ patches PASS 234.28 seconds
Scan Build PASS 617.84 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-08-16 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 22:05 [BlueZ PATCH v2 1/2] hog-lib: Don't restrict Report MAP size Luiz Augusto von Dentz
2022-08-16 22:05 ` [BlueZ PATCH v2 2/2] hog-lib: Fix scan-build error Luiz Augusto von Dentz
2022-08-16 23:13 ` bluez.test.bot [this message]
2022-08-16 23:20 ` [BlueZ PATCH v2 1/2] hog-lib: Don't restrict Report MAP size 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=62fc24b0.a70a0220.b7101.ef6f@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