From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, jonas@dptechnics.com
Subject: RE: Fix bug where bluetooth-meshd stops sending
Date: Fri, 10 Jun 2022 10:03:39 -0700 (PDT) [thread overview]
Message-ID: <62a3796b.1c69fb81.8afdb.1f4b@mx.google.com> (raw)
In-Reply-To: <20220610152902.21677-2-jonas@dptechnics.com>
[-- Attachment #1: Type: text/plain, Size: 996 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=649335
---Test result---
Test Summary:
CheckPatch PASS 0.60 seconds
GitLint PASS 0.36 seconds
Prep - Setup ELL PASS 51.48 seconds
Build - Prep PASS 0.59 seconds
Build - Configure PASS 9.86 seconds
Build - Make PASS 1784.55 seconds
Make Check PASS 12.38 seconds
Make Check w/Valgrind PASS 531.01 seconds
Make Distcheck PASS 281.18 seconds
Build w/ext ELL - Configure PASS 10.16 seconds
Build w/ext ELL - Make PASS 1768.46 seconds
Incremental Build with patchesPASS 0.00 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-06-10 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 15:29 [PATCH BlueZ 0/1] Fix bug where bluetooth-meshd stops sending Jonas Maes
2022-06-10 15:29 ` [PATCH BlueZ 1/1] " Jonas Maes
2022-06-10 17:03 ` bluez.test.bot [this message]
2022-06-21 20:20 ` [PATCH BlueZ 0/1] " patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2022-06-09 9:08 [PATCH BlueZ 1/1] " Jonas Maes
2022-06-09 11:02 ` 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=62a3796b.1c69fb81.8afdb.1f4b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=jonas@dptechnics.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.