From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, frederic.danis@collabora.com
Subject: RE: [BlueZ,1/2] obexd/client/map: Add SupportedTypes property to MessageAccess1
Date: Thu, 20 Feb 2025 00:29:14 -0800 (PST) [thread overview]
Message-ID: <67b6e7da.050a0220.2fdd70.4e70@mx.google.com> (raw)
In-Reply-To: <20250220072446.190256-1-frederic.danis@collabora.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=935872
---Test result---
Test Summary:
CheckPatch PENDING 0.20 seconds
GitLint PENDING 0.24 seconds
BuildEll PASS 20.18 seconds
BluezMake PASS 1469.28 seconds
MakeCheck PASS 22.35 seconds
MakeDistcheck PASS 155.80 seconds
CheckValgrind PASS 212.05 seconds
CheckSmatch PASS 281.72 seconds
bluezmakeextell PASS 97.19 seconds
IncrementalBuild PENDING 0.22 seconds
ScanBuild PASS 848.62 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-02-20 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 7:24 [PATCH BlueZ 1/2] obexd/client/map: Add SupportedTypes property to MessageAccess1 Frédéric Danis
2025-02-20 7:24 ` [PATCH BlueZ 2/2] doc: " Frédéric Danis
2025-02-20 8:29 ` bluez.test.bot [this message]
2025-02-21 16:50 ` [PATCH BlueZ 1/2] obexd/client/map: " 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=67b6e7da.050a0220.2fdd70.4e70@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=frederic.danis@collabora.com \
--cc=linux-bluetooth@vger.kernel.org \
/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.