From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, isak.westin@loytec.com
Subject: RE: Mesh: Fix heartbeat publication/subscription
Date: Mon, 26 Sep 2022 08:54:04 -0700 (PDT) [thread overview]
Message-ID: <6331cb1c.170a0220.2d0e6.4cbd@mx.google.com> (raw)
In-Reply-To: <20220926130110.2146-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=680522
---Test result---
Test Summary:
CheckPatch PASS 3.06 seconds
GitLint PASS 2.07 seconds
Prep - Setup ELL PASS 35.30 seconds
Build - Prep PASS 0.83 seconds
Build - Configure PASS 10.94 seconds
Build - Make PASS 1231.41 seconds
Make Check PASS 13.40 seconds
Make Check w/Valgrind PASS 380.05 seconds
Make Distcheck PASS 324.29 seconds
Build w/ext ELL - Configure PASS 11.27 seconds
Build w/ext ELL - Make PASS 115.80 seconds
Incremental Build w/ patches PASS 538.07 seconds
Scan Build PASS 738.03 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-09-26 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 13:01 [PATCH BlueZ 0/4] Mesh: Fix heartbeat publication/subscription Isak Westin
2022-09-26 13:01 ` [PATCH BlueZ 1/4] mesh: Correct u32 to u8 log transformation Isak Westin
2022-09-26 15:54 ` bluez.test.bot [this message]
2022-09-26 13:01 ` [PATCH BlueZ 2/4] mesh: Reply to HB pub set with same fields Isak Westin
2022-09-26 13:01 ` [PATCH BlueZ 3/4] mesh: Correct HB sub state updates Isak Westin
2022-09-26 13:01 ` [PATCH BlueZ 4/4] mesh: Clear HB sub status field if disabled Isak Westin
2022-09-26 20:20 ` [PATCH BlueZ 0/4] Mesh: Fix heartbeat publication/subscription 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=6331cb1c.170a0220.2d0e6.4cbd@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 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.