From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, dan.gora@gmail.com
Subject: RE: [1/1] Bluetooth: btrtl: Add missing MODULE_FIRMWARE declarations.
Date: Thu, 04 May 2023 14:56:57 -0700 (PDT) [thread overview]
Message-ID: <64542a29.6b0a0220.37447.00af@mx.google.com> (raw)
In-Reply-To: <20230504212843.18519-1-dan.gora@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2043 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=745113
---Test result---
Test Summary:
CheckPatch PASS 0.62 seconds
GitLint FAIL 0.54 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 32.49 seconds
CheckAllWarning PASS 35.43 seconds
CheckSparse PASS 40.11 seconds
CheckSmatch PASS 108.90 seconds
BuildKernel32 PASS 31.32 seconds
TestRunnerSetup PASS 445.68 seconds
TestRunner_l2cap-tester PASS 17.26 seconds
TestRunner_iso-tester PASS 21.37 seconds
TestRunner_bnep-tester PASS 5.61 seconds
TestRunner_mgmt-tester PASS 117.27 seconds
TestRunner_rfcomm-tester PASS 9.05 seconds
TestRunner_sco-tester PASS 8.30 seconds
TestRunner_ioctl-tester PASS 9.74 seconds
TestRunner_mesh-tester PASS 7.15 seconds
TestRunner_smp-tester PASS 8.16 seconds
TestRunner_userchan-tester PASS 5.91 seconds
IncrementalBuild PASS 29.61 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[1/1] Bluetooth: btrtl: Add missing MODULE_FIRMWARE declarations.
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
1: T3 Title has trailing punctuation (.): "[1/1] Bluetooth: btrtl: Add missing MODULE_FIRMWARE declarations."
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-05-04 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 21:28 [PATCH 1/1] Bluetooth: btrtl: Add missing MODULE_FIRMWARE declarations Dan Gora
2023-05-04 21:56 ` bluez.test.bot [this message]
2023-05-09 19:45 ` [PATCH v2 1/1] Bluetooth: btusb: Add device 6655:8771 to device tables Dan Gora
2023-05-09 20:41 ` [v2,1/1] " bluez.test.bot
2023-05-12 20:40 ` [PATCH v2 1/1] " patchwork-bot+bluetooth
2023-05-09 19:51 ` [PATCH v2 1/1] Bluetooth: btrtl: Add missing MODULE_FIRMWARE declarations Dan Gora
2023-05-09 20:40 ` [v2,1/1] " bluez.test.bot
2023-05-12 20:40 ` [PATCH v2 1/1] " patchwork-bot+bluetooth
2024-06-10 14:20 ` Vitaly Chikunov
2023-05-12 20:40 ` [PATCH " 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=64542a29.6b0a0220.37447.00af@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=dan.gora@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.