From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/5] att: Log file and function names
Date: Mon, 21 Mar 2022 17:33:01 -0700 (PDT) [thread overview]
Message-ID: <6239193d.1c69fb81.99c4f.209d@mx.google.com> (raw)
In-Reply-To: <20220321205529.2469387-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 998 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=625273
---Test result---
Test Summary:
CheckPatch PASS 7.48 seconds
GitLint PASS 5.00 seconds
Prep - Setup ELL PASS 44.76 seconds
Build - Prep PASS 0.75 seconds
Build - Configure PASS 9.00 seconds
Build - Make PASS 1526.60 seconds
Make Check PASS 11.54 seconds
Make Check w/Valgrind PASS 461.85 seconds
Make Distcheck PASS 264.50 seconds
Build w/ext ELL - Configure PASS 9.28 seconds
Build w/ext ELL - Make PASS 1521.31 seconds
Incremental Build with patchesPASS 7600.04 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-03-22 0:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 20:55 [PATCH BlueZ 1/5] att: Log file and function names Luiz Augusto von Dentz
2022-03-21 20:55 ` [PATCH BlueZ 2/5] device: Don't use DBG in gatt_debug Luiz Augusto von Dentz
2022-03-21 20:55 ` [PATCH BlueZ 3/5] gatt-client: Add DBG macro Luiz Augusto von Dentz
2022-03-21 20:55 ` [PATCH BlueZ 4/5] gatt-server: " Luiz Augusto von Dentz
2022-03-21 20:55 ` [PATCH BlueZ 5/5] att: Rename att_debug and att_verbose to DBG and VERBOSE Luiz Augusto von Dentz
2022-03-22 0:33 ` bluez.test.bot [this message]
2022-03-24 19:50 ` [PATCH BlueZ 1/5] att: Log file and function names 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=6239193d.1c69fb81.99c4f.209d@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 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.