From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, gioele@svario.it
Subject: RE: configure.ac: Install D-Bus policy in /usr/share, not /etc
Date: Wed, 09 Aug 2023 01:25:56 -0700 (PDT) [thread overview]
Message-ID: <64d34d94.0c0a0220.98f04.19f1@mx.google.com> (raw)
In-Reply-To: <20230809065143.2002324-2-gioele@svario.it>
[-- Attachment #1: Type: text/plain, Size: 948 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=774393
---Test result---
Test Summary:
CheckPatch PASS 0.95 seconds
GitLint PASS 0.69 seconds
BuildEll PASS 27.58 seconds
BluezMake PASS 889.39 seconds
MakeCheck PASS 12.96 seconds
MakeDistcheck PASS 159.07 seconds
CheckValgrind PASS 258.58 seconds
CheckSmatch PASS 347.14 seconds
bluezmakeextell PASS 105.28 seconds
IncrementalBuild PASS 1470.25 seconds
ScanBuild PASS 1075.30 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-08-09 8:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 6:51 [PATCH BlueZ v4 0/2] configure.ac: Install D-Bus policy in /usr/share, not /etc Gioele Barabucci
2023-08-09 6:51 ` [PATCH BlueZ v4 1/2] configure.ac: Bump minimum D-Bus version to 1.10 Gioele Barabucci
2023-08-09 8:25 ` bluez.test.bot [this message]
2023-08-09 6:51 ` [PATCH BlueZ v4 2/2] configure.ac: Install D-Bus policy in /usr/share, not /etc Gioele Barabucci
2023-08-09 18:20 ` [PATCH BlueZ v4 0/2] " patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2023-08-09 6:44 [PATCH BlueZ v3 1/2] configure.ac: Bump minimum D-Bus version to 1.10 Gioele Barabucci
2023-08-09 8:24 ` configure.ac: Install D-Bus policy in /usr/share, not /etc bluez.test.bot
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=64d34d94.0c0a0220.98f04.19f1@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=gioele@svario.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox