From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kiran.k@intel.com
Subject: RE: Bluetooth:btintel: Print firmware SHA1
Date: Thu, 23 Nov 2023 06:56:39 -0800 (PST) [thread overview]
Message-ID: <655f6827.d40a0220.ade93.07b2@mx.google.com> (raw)
In-Reply-To: <20231123143550.2436697-1-kiran.k@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1597 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=803732
---Test result---
Test Summary:
CheckPatch PASS 0.77 seconds
GitLint PASS 0.31 seconds
SubjectPrefix FAIL 1.45 seconds
BuildKernel PASS 27.53 seconds
CheckAllWarning PASS 30.26 seconds
CheckSparse PASS 35.44 seconds
CheckSmatch PASS 98.88 seconds
BuildKernel32 PASS 26.81 seconds
TestRunnerSetup PASS 414.87 seconds
TestRunner_l2cap-tester PASS 23.12 seconds
TestRunner_iso-tester PASS 41.17 seconds
TestRunner_bnep-tester PASS 6.92 seconds
TestRunner_mgmt-tester PASS 166.72 seconds
TestRunner_rfcomm-tester PASS 10.85 seconds
TestRunner_sco-tester PASS 14.58 seconds
TestRunner_ioctl-tester PASS 12.05 seconds
TestRunner_mesh-tester PASS 8.84 seconds
TestRunner_smp-tester PASS 9.84 seconds
TestRunner_userchan-tester PASS 7.33 seconds
IncrementalBuild PASS 26.60 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:[~2023-11-23 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 14:35 [PATCH] Bluetooth:btintel: Print firmware SHA1 Kiran K
2023-11-23 14:56 ` bluez.test.bot [this message]
2023-11-27 15:20 ` patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2023-11-27 4:42 [PATCH] Bluetooth: btintel: " Kiran K
2023-11-27 4:58 ` 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=655f6827.d40a0220.ade93.07b2@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=kiran.k@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox