From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, isak.westin@loytec.com
Subject: RE: Mesh: Fixes for friendship procedures
Date: Tue, 04 Oct 2022 02:32:51 -0700 (PDT) [thread overview]
Message-ID: <633bfdc3.170a0220.c0279.6a25@mx.google.com> (raw)
In-Reply-To: <20221004082530.25719-2-isak.westin@loytec.com>
[-- Attachment #1: Type: text/plain, Size: 1053 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=682931
---Test result---
Test Summary:
CheckPatch PASS 2.69 seconds
GitLint PASS 1.83 seconds
Prep - Setup ELL PASS 32.77 seconds
Build - Prep PASS 0.79 seconds
Build - Configure PASS 10.20 seconds
Build - Make PASS 1074.82 seconds
Make Check PASS 12.10 seconds
Make Check w/Valgrind PASS 347.39 seconds
Make Distcheck PASS 287.27 seconds
Build w/ext ELL - Configure PASS 10.21 seconds
Build w/ext ELL - Make PASS 104.52 seconds
Incremental Build w/ patches PASS 492.04 seconds
Scan Build PASS 642.46 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-10-04 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 8:25 [PATCH BlueZ 0/4] Mesh: Fixes for friendship procedures Isak Westin
2022-10-04 8:25 ` [PATCH BlueZ 1/4] mesh: Correct size of friend cache Isak Westin
2022-10-04 9:32 ` bluez.test.bot [this message]
2022-10-04 8:25 ` [PATCH BlueZ 2/4] mesh: Verify padding bits in Friend Poll messages Isak Westin
2022-10-04 8:25 ` [PATCH BlueZ 3/4] mesh: Queue a friend update on IV Update change Isak Westin
2022-10-04 8:25 ` [PATCH BlueZ 4/4] mesh: Always relay messages from Low Power nodes Isak Westin
2022-10-06 20:59 ` [PATCH BlueZ 0/4] Mesh: Fixes for friendship procedures Gix, Brian
2022-10-06 21:00 ` 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=633bfdc3.170a0220.c0279.6a25@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=isak.westin@loytec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).