From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/2] gatt: Print error if gatt_db_attribut_notify fails
Date: Mon, 14 Mar 2022 17:15:24 -0700 (PDT) [thread overview]
Message-ID: <622fda9c.1c69fb81.91a3a.2164@mx.google.com> (raw)
In-Reply-To: <20220314215010.23822-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=623328
---Test result---
Test Summary:
CheckPatch PASS 1.36 seconds
GitLint PASS 0.91 seconds
Prep - Setup ELL PASS 49.35 seconds
Build - Prep PASS 0.52 seconds
Build - Configure PASS 9.55 seconds
Build - Make PASS 1419.91 seconds
Make Check PASS 12.00 seconds
Make Check w/Valgrind PASS 510.87 seconds
Make Distcheck PASS 265.65 seconds
Build w/ext ELL - Configure PASS 9.87 seconds
Build w/ext ELL - Make PASS 1390.20 seconds
Incremental Build with patchesPASS 2873.48 seconds
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2022-03-15 0:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 21:50 [PATCH BlueZ 1/2] gatt: Print error if gatt_db_attribut_notify fails Luiz Augusto von Dentz
2022-03-14 21:50 ` [PATCH BlueZ 2/2] gatt-db: Fix gatt_db_attribute_notify Luiz Augusto von Dentz
2022-03-14 23:40 ` [PATCH BlueZ 1/2] gatt: Print error if gatt_db_attribut_notify fails patchwork-bot+bluetooth
2022-03-15 0:15 ` 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=622fda9c.1c69fb81.91a3a.2164@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.