From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: [1/4] build: Always define confdir and statedir
Date: Wed, 26 Jan 2022 06:07:18 -0800 (PST) [thread overview]
Message-ID: <61f15596.1c69fb81.ba6f2.d20a@mx.google.com> (raw)
In-Reply-To: <20220126113638.1706785-1-hadess@hadess.net>
[-- 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=608628
---Test result---
Test Summary:
CheckPatch PASS 5.68 seconds
GitLint PASS 3.84 seconds
Prep - Setup ELL PASS 41.84 seconds
Build - Prep PASS 0.71 seconds
Build - Configure PASS 8.38 seconds
Build - Make PASS 1292.67 seconds
Make Check PASS 11.33 seconds
Make Check w/Valgrind PASS 448.95 seconds
Make Distcheck PASS 231.67 seconds
Build w/ext ELL - Configure PASS 8.74 seconds
Build w/ext ELL - Make PASS 1305.94 seconds
Incremental Build with patchesPASS 5303.63 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-01-26 14:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 11:36 [PATCH 1/4] build: Always define confdir and statedir Bastien Nocera
2022-01-26 11:36 ` [PATCH 2/4] systemd: Add PrivateTmp and NoNewPrivileges options Bastien Nocera
2022-01-26 11:36 ` [PATCH 3/4] systemd: Add more filesystem lockdown Bastien Nocera
2022-01-26 11:36 ` [PATCH 4/4] systemd: More lockdown Bastien Nocera
2022-01-26 11:38 ` [PATCH 1/4] build: Always define confdir and statedir Bastien Nocera
2022-01-26 13:31 ` Marcel Holtmann
2022-01-26 13:45 ` Bastien Nocera
2022-02-01 9:32 ` Bastien Nocera
2022-04-12 19:48 ` Luiz Augusto von Dentz
2022-01-26 14:07 ` bluez.test.bot [this message]
2022-01-31 18:45 ` [1/4] " Luiz Augusto von Dentz
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=61f15596.1c69fb81.ba6f2.d20a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hadess@hadess.net \
--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