From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, dengshaomin@cdjrlc.com
Subject: RE: Bluetooth:btrtl:Fix typo in comment
Date: Tue, 19 Jul 2022 09:10:40 -0700 (PDT) [thread overview]
Message-ID: <62d6d780.1c69fb81.dc274.1ae0@mx.google.com> (raw)
In-Reply-To: <20220719154148.16769-1-dengshaomin@cdjrlc.com>
[-- Attachment #1: Type: text/plain, Size: 1266 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=661165
---Test result---
Test Summary:
CheckPatch PASS 1.13 seconds
GitLint PASS 0.54 seconds
SubjectPrefix FAIL 0.40 seconds
BuildKernel PASS 33.58 seconds
BuildKernel32 PASS 28.97 seconds
Incremental Build with patchesPASS 41.56 seconds
TestRunner: Setup PASS 497.27 seconds
TestRunner: l2cap-tester PASS 16.71 seconds
TestRunner: bnep-tester PASS 5.57 seconds
TestRunner: mgmt-tester PASS 96.20 seconds
TestRunner: rfcomm-tester PASS 8.98 seconds
TestRunner: sco-tester PASS 8.72 seconds
TestRunner: smp-tester PASS 8.80 seconds
TestRunner: userchan-tester PASS 5.75 seconds
Details
##############################
Test: SubjectPrefix - FAIL - 0.40 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-07-19 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 15:41 [PATCH] Bluetooth:btrtl:Fix typo in comment shaomin Deng
2022-07-19 16:10 ` bluez.test.bot [this message]
2022-07-19 19:28 ` Paul Menzel
-- strict thread matches above, loose matches on Subject: below --
2022-07-20 14:10 [PATCH] Bluetooth: btrtl: Fix " shaomin Deng
2022-07-20 15:02 ` 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=62d6d780.1c69fb81.dc274.1ae0@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=dengshaomin@cdjrlc.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;
as well as URLs for NNTP newsgroup(s).