From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, Larry.Finger@lwfinger.net
Subject: RE: [v2] bluetooth: Add device 0bda:4853 to device tables
Date: Tue, 08 Aug 2023 19:24:03 -0700 (PDT) [thread overview]
Message-ID: <64d2f8c3.0c0a0220.7ae79.0af9@mx.google.com> (raw)
In-Reply-To: <20230809010403.24612-1-Larry.Finger@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 1602 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=774317
---Test result---
Test Summary:
CheckPatch PASS 0.68 seconds
GitLint PASS 0.33 seconds
SubjectPrefix FAIL 0.31 seconds
BuildKernel PASS 32.44 seconds
CheckAllWarning PASS 35.90 seconds
CheckSparse PASS 40.84 seconds
CheckSmatch PASS 113.59 seconds
BuildKernel32 PASS 31.60 seconds
TestRunnerSetup PASS 478.91 seconds
TestRunner_l2cap-tester PASS 22.21 seconds
TestRunner_iso-tester PASS 45.12 seconds
TestRunner_bnep-tester PASS 10.05 seconds
TestRunner_mgmt-tester PASS 212.22 seconds
TestRunner_rfcomm-tester PASS 15.32 seconds
TestRunner_sco-tester PASS 18.29 seconds
TestRunner_ioctl-tester PASS 17.10 seconds
TestRunner_mesh-tester PASS 12.73 seconds
TestRunner_smp-tester PASS 13.63 seconds
TestRunner_userchan-tester PASS 10.51 seconds
IncrementalBuild PASS 30.03 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-08-09 2:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 1:04 [PATCH v2] bluetooth: Add device 0bda:4853 to device tables Larry Finger
2023-08-09 2:24 ` bluez.test.bot [this message]
2023-08-09 5:58 ` Paul Menzel
2023-08-09 17:41 ` Larry Finger
2023-08-11 17:30 ` patchwork-bot+bluetooth
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=64d2f8c3.0c0a0220.7ae79.0af9@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=Larry.Finger@lwfinger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox