From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luca@z3ntu.xyz
Subject: RE: [v3] dt-bindings: bluetooth: broadcom: add BCM43430A0 & BCM43430A1
Date: Sat, 24 Sep 2022 08:04:55 -0700 (PDT) [thread overview]
Message-ID: <632f1c97.050a0220.44105.ca6a@mx.google.com> (raw)
In-Reply-To: <20220924142154.14217-1-luca@z3ntu.xyz>
[-- Attachment #1: Type: text/plain, Size: 1376 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=680145
---Test result---
Test Summary:
CheckPatch PASS 1.68 seconds
GitLint PASS 1.07 seconds
SubjectPrefix FAIL 0.90 seconds
BuildKernel PASS 34.77 seconds
BuildKernel32 PASS 31.30 seconds
Incremental Build with patchesPASS 45.59 seconds
TestRunner: Setup PASS 513.04 seconds
TestRunner: l2cap-tester PASS 17.24 seconds
TestRunner: iso-tester PASS 16.11 seconds
TestRunner: bnep-tester PASS 6.59 seconds
TestRunner: mgmt-tester PASS 104.39 seconds
TestRunner: rfcomm-tester PASS 10.43 seconds
TestRunner: sco-tester PASS 9.81 seconds
TestRunner: ioctl-tester PASS 11.00 seconds
TestRunner: smp-tester PASS 9.94 seconds
TestRunner: userchan-tester PASS 6.86 seconds
Details
##############################
Test: SubjectPrefix - FAIL - 0.90 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-09-24 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 14:21 [PATCH v3] dt-bindings: bluetooth: broadcom: add BCM43430A0 & BCM43430A1 Luca Weiss
2022-09-24 15:04 ` bluez.test.bot [this message]
2022-11-18 17:13 ` Luca Weiss
2022-11-21 14:00 ` Linus Walleij
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=632f1c97.050a0220.44105.ca6a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luca@z3ntu.xyz \
/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