From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, brgl@bgdev.pl
Subject: RE: [1/2] Bluetooth: qca: add regulators for QCA6390
Date: Tue, 05 Dec 2023 03:57:12 -0800 (PST) [thread overview]
Message-ID: <656f1018.630a0220.3a3b3.9e55@mx.google.com> (raw)
In-Reply-To: <20231205110903.68898-1-brgl@bgdev.pl>
[-- Attachment #1: Type: text/plain, Size: 1423 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=806985
---Test result---
Test Summary:
CheckPatch PASS 0.96 seconds
GitLint PASS 0.46 seconds
SubjectPrefix PASS 0.17 seconds
BuildKernel PASS 27.72 seconds
CheckAllWarning PASS 30.13 seconds
CheckSparse PASS 35.27 seconds
CheckSmatch PASS 100.73 seconds
BuildKernel32 PASS 26.72 seconds
TestRunnerSetup PASS 418.81 seconds
TestRunner_l2cap-tester PASS 22.99 seconds
TestRunner_iso-tester PASS 46.47 seconds
TestRunner_bnep-tester PASS 6.96 seconds
TestRunner_mgmt-tester PASS 162.23 seconds
TestRunner_rfcomm-tester PASS 10.84 seconds
TestRunner_sco-tester PASS 14.47 seconds
TestRunner_ioctl-tester PASS 12.11 seconds
TestRunner_mesh-tester PASS 8.85 seconds
TestRunner_smp-tester PASS 9.76 seconds
TestRunner_userchan-tester PASS 7.34 seconds
IncrementalBuild PASS 30.36 seconds
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-12-05 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 11:09 [PATCH 1/2] Bluetooth: qca: add regulators for QCA6390 Bartosz Golaszewski
2023-12-05 11:09 ` [PATCH 2/2] Bluetooth: qca: run the power-on/off sequence for QCA6390 too Bartosz Golaszewski
2023-12-05 11:47 ` Johan Hovold
2023-12-05 11:57 ` 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=656f1018.630a0220.3a3b3.9e55@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=brgl@bgdev.pl \
--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.