From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: [BlueZ,v5,1/6] adapter: Keep track of whether the adapter is rfkill'ed
Date: Wed, 31 Aug 2022 05:41:43 -0700 (PDT) [thread overview]
Message-ID: <630f5707.170a0220.44682.cf2e@mx.google.com> (raw)
In-Reply-To: <20220831113647.85110-1-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 1052 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=672790
---Test result---
Test Summary:
CheckPatch PASS 4.25 seconds
GitLint PASS 2.84 seconds
Prep - Setup ELL PASS 34.13 seconds
Build - Prep PASS 0.78 seconds
Build - Configure PASS 11.35 seconds
Build - Make PASS 997.08 seconds
Make Check PASS 12.88 seconds
Make Check w/Valgrind PASS 356.54 seconds
Make Distcheck PASS 329.05 seconds
Build w/ext ELL - Configure PASS 11.76 seconds
Build w/ext ELL - Make PASS 103.97 seconds
Incremental Build w/ patches PASS 748.41 seconds
Scan Build PASS 812.42 seconds
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2022-08-31 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 11:36 [PATCH BlueZ v5 1/6] adapter: Keep track of whether the adapter is rfkill'ed Bastien Nocera
2022-08-31 11:36 ` [PATCH BlueZ v5 2/6] adapter: Implement PowerState property Bastien Nocera
2022-08-31 11:36 ` [PATCH BlueZ v5 3/6] client: Print the " Bastien Nocera
2022-08-31 11:36 ` [PATCH BlueZ v5 4/6] adapter-api: Add PowerState property documentation Bastien Nocera
2022-08-31 20:43 ` Luiz Augusto von Dentz
2022-09-01 10:43 ` Bastien Nocera
2022-08-31 11:36 ` [PATCH BlueZ v5 5/6] adapter: Fix typo in function name Bastien Nocera
2022-08-31 11:36 ` [PATCH BlueZ v5 6/6] adapter: Remove experimental flag for PowerState Bastien Nocera
2022-08-31 12:41 ` bluez.test.bot [this message]
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=630f5707.170a0220.44682.cf2e@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 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.