From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1,1/2] org.bluez.GattCharacteristic: Add confirmation support to AcquireNotify
Date: Tue, 28 Jan 2025 10:07:32 -0800 (PST) [thread overview]
Message-ID: <67991ce4.050a0220.155ff3.486a@mx.google.com> (raw)
In-Reply-To: <20250128165424.1044479-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1260 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=928892
---Test result---
Test Summary:
CheckPatch PENDING 0.21 seconds
GitLint PENDING 0.24 seconds
BuildEll PASS 20.08 seconds
BluezMake PASS 1559.01 seconds
MakeCheck PASS 13.12 seconds
MakeDistcheck PASS 156.65 seconds
CheckValgrind PASS 212.54 seconds
CheckSmatch PASS 267.63 seconds
bluezmakeextell PASS 97.26 seconds
IncrementalBuild PENDING 0.35 seconds
ScanBuild PASS 844.59 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-01-28 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 16:54 [PATCH BlueZ v1 1/2] org.bluez.GattCharacteristic: Add confirmation support to AcquireNotify Luiz Augusto von Dentz
2025-01-28 16:54 ` [PATCH BlueZ v1 2/2] gatt: Implement confirmation support for AcquireNotify Luiz Augusto von Dentz
2025-01-28 18:07 ` bluez.test.bot [this message]
2025-01-30 16:30 ` [PATCH BlueZ v1 1/2] org.bluez.GattCharacteristic: Add confirmation support to AcquireNotify 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=67991ce4.050a0220.155ff3.486a@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.