From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, brgl@bgdev.pl
Subject: RE: clk: implement a new managed helper and add first user
Date: Mon, 05 Aug 2024 02:35:57 -0700 (PDT) [thread overview]
Message-ID: <66b09cfd.050a0220.ac4f0.9dde@mx.google.com> (raw)
In-Reply-To: <20240805-clk-new-helper-v2-1-e5fdd1e1d729@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1596 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=876621
---Test result---
Test Summary:
CheckPatch PASS 1.54 seconds
GitLint PASS 0.98 seconds
SubjectPrefix FAIL 0.56 seconds
BuildKernel PASS 30.19 seconds
CheckAllWarning PASS 33.30 seconds
CheckSparse PASS 38.25 seconds
CheckSmatch PASS 105.38 seconds
BuildKernel32 PASS 30.05 seconds
TestRunnerSetup PASS 538.80 seconds
TestRunner_l2cap-tester PASS 20.72 seconds
TestRunner_iso-tester PASS 33.48 seconds
TestRunner_bnep-tester PASS 4.93 seconds
TestRunner_mgmt-tester PASS 115.35 seconds
TestRunner_rfcomm-tester PASS 7.59 seconds
TestRunner_sco-tester PASS 15.24 seconds
TestRunner_ioctl-tester PASS 8.16 seconds
TestRunner_mesh-tester PASS 6.17 seconds
TestRunner_smp-tester PASS 7.05 seconds
TestRunner_userchan-tester PASS 5.11 seconds
IncrementalBuild PASS 33.70 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-08-05 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 8:57 [PATCH v2 0/2] clk: implement a new managed helper and add first user Bartosz Golaszewski
2024-08-05 8:57 ` [PATCH v2 1/2] clk: provide devm_clk_get_optional_enabled_with_rate() Bartosz Golaszewski
2024-08-05 9:35 ` bluez.test.bot [this message]
2024-09-05 21:42 ` Stephen Boyd
2024-09-09 6:41 ` Bartosz Golaszewski
2024-08-05 8:57 ` [PATCH v2 2/2] Bluetooth: hci_qca: use devm_clk_get_optional_enabled_with_rate() Bartosz Golaszewski
2024-09-02 8:33 ` [PATCH v2 0/2] clk: implement a new managed helper and add first user Bartosz Golaszewski
-- strict thread matches above, loose matches on Subject: below --
2024-08-01 15:58 [PATCH RFC 1/2] clk: provide devm_clk_get_optional_enabled_with_rate() Bartosz Golaszewski
2024-08-01 16:37 ` clk: implement a new managed helper and add first user 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=66b09cfd.050a0220.ac4f0.9dde@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox