From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, dimitri.ledkov@canonical.com
Subject: RE: Bluetooth: btintel: Correctly declare all module firmware files.
Date: Mon, 09 May 2022 10:26:23 -0700 (PDT) [thread overview]
Message-ID: <62794ebf.1c69fb81.9e08e.6873@mx.google.com> (raw)
In-Reply-To: <20220509163259.1513242-1-dimitri.ledkov@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1382 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=639836
---Test result---
Test Summary:
CheckPatch PASS 1.59 seconds
GitLint FAIL 0.99 seconds
SubjectPrefix PASS 0.93 seconds
BuildKernel PASS 31.76 seconds
BuildKernel32 PASS 28.69 seconds
Incremental Build with patchesPASS 38.90 seconds
TestRunner: Setup PASS 475.73 seconds
TestRunner: l2cap-tester PASS 17.45 seconds
TestRunner: bnep-tester PASS 6.16 seconds
TestRunner: mgmt-tester PASS 102.48 seconds
TestRunner: rfcomm-tester PASS 9.62 seconds
TestRunner: sco-tester PASS 9.46 seconds
TestRunner: smp-tester PASS 9.42 seconds
TestRunner: userchan-tester PASS 6.37 seconds
Details
##############################
Test: GitLint - FAIL - 0.99 seconds
Run gitlint with rule in .gitlint
Bluetooth: btintel: Correctly declare all module firmware files.
1: T3 Title has trailing punctuation (.): "Bluetooth: btintel: Correctly declare all module firmware files."
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-05-09 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 16:32 [PATCH] Bluetooth: btintel: Correctly declare all module firmware files Dimitri John Ledkov
2022-05-09 17:26 ` bluez.test.bot [this message]
2022-05-13 11:15 ` Marcel Holtmann
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=62794ebf.1c69fb81.9e08e.6873@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=dimitri.ledkov@canonical.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).