From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, christophe.jaillet@wanadoo.fr
Subject: RE: [v3] Bluetooth: hci_debugfs: Use kstrtobool() instead of strtobool()
Date: Tue, 11 Jul 2023 11:40:01 -0700 (PDT) [thread overview]
Message-ID: <64ada201.c80a0220.87a99.5110@mx.google.com> (raw)
In-Reply-To: <58247d1b8105739f0371030a93fb28ea3dbedc57.1673687451.git.christophe.jaillet@wanadoo.fr>
[-- Attachment #1: Type: text/plain, Size: 2277 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=764536
---Test result---
Test Summary:
CheckPatch PASS 0.69 seconds
GitLint FAIL 0.63 seconds
SubjectPrefix PASS 0.14 seconds
BuildKernel PASS 33.35 seconds
CheckAllWarning PASS 36.61 seconds
CheckSparse PASS 41.58 seconds
CheckSmatch PASS 114.87 seconds
BuildKernel32 PASS 32.08 seconds
TestRunnerSetup PASS 487.74 seconds
TestRunner_l2cap-tester PASS 22.52 seconds
TestRunner_iso-tester PASS 40.30 seconds
TestRunner_bnep-tester PASS 10.19 seconds
TestRunner_mgmt-tester PASS 214.76 seconds
TestRunner_rfcomm-tester PASS 15.63 seconds
TestRunner_sco-tester PASS 16.55 seconds
TestRunner_ioctl-tester PASS 17.22 seconds
TestRunner_mesh-tester PASS 12.98 seconds
TestRunner_smp-tester PASS 13.79 seconds
TestRunner_userchan-tester PASS 10.69 seconds
IncrementalBuild PASS 30.56 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v3] Bluetooth: hci_debugfs: Use kstrtobool() instead of strtobool()
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
29: B1 Line exceeds max length (118>80): " - https://lore.kernel.org/all/58207d5b81c5739c037c030893fb08ea3dbedc57.1673687451.git.christophe.jaillet@wanadoo.fr/"
31: B2 Line has trailing whitespace: "v1: "
32: B1 Line exceeds max length (84>80): "[1]: https://lore.kernel.org/all/cover.1667336095.git.christophe.jaillet@wanadoo.fr/"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-07-11 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 17:41 [PATCH v3] Bluetooth: hci_debugfs: Use kstrtobool() instead of strtobool() Christophe JAILLET
2023-07-11 18:40 ` bluez.test.bot [this message]
2023-07-12 21:10 ` 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=64ada201.c80a0220.87a99.5110@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--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).