From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v3] Bluetooth: HCI: Introduce HCI_QUIRK_BROKEN_LE_CODED
Date: Tue, 22 Aug 2023 17:05:41 -0700 (PDT) [thread overview]
Message-ID: <64e54d55.050a0220.31b08.e540@mx.google.com> (raw)
In-Reply-To: <20230822232340.3780478-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3052 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=778385
---Test result---
Test Summary:
CheckPatch FAIL 1.59 seconds
GitLint FAIL 0.58 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 42.38 seconds
CheckAllWarning PASS 43.33 seconds
CheckSparse PASS 47.76 seconds
CheckSmatch PASS 132.12 seconds
BuildKernel32 PASS 37.90 seconds
TestRunnerSetup PASS 588.26 seconds
TestRunner_l2cap-tester PASS 34.75 seconds
TestRunner_iso-tester PASS 73.94 seconds
TestRunner_bnep-tester PASS 14.30 seconds
TestRunner_mgmt-tester PASS 271.92 seconds
TestRunner_rfcomm-tester PASS 20.80 seconds
TestRunner_sco-tester PASS 24.33 seconds
TestRunner_ioctl-tester PASS 23.27 seconds
TestRunner_mesh-tester PASS 17.40 seconds
TestRunner_smp-tester PASS 18.49 seconds
TestRunner_userchan-tester PASS 14.45 seconds
IncrementalBuild PASS 36.60 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v3] Bluetooth: HCI: Introduce HCI_QUIRK_BROKEN_LE_CODED
WARNING: quoted string split across lines
#166: FILE: net/bluetooth/hci_sync.c:4671:
"HCI LE Set Random Private Address Timeout command is "
+ "advertised, but not supported."),
WARNING: quoted string split across lines
#169: FILE: net/bluetooth/hci_sync.c:4674:
+ "HCI LE Coded PHY feature bit is set, "
+ "but its usage is not supported.")
total: 0 errors, 2 warnings, 0 checks, 55 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/src/13361520.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v3] Bluetooth: HCI: Introduce HCI_QUIRK_BROKEN_LE_CODED
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
11: B1 Line exceeds max length (116>80): "Link: https://lore.kernel.org/linux-bluetooth/CABBYNZKco-v7wkjHHexxQbgwwSz-S=GZ=dZKbRE1qxT1h4fFbQ@mail.gmail.com/T/#"
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-08-23 0:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 23:23 [PATCH v3] Bluetooth: HCI: Introduce HCI_QUIRK_BROKEN_LE_CODED Luiz Augusto von Dentz
2023-08-23 0:05 ` bluez.test.bot [this message]
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=64e54d55.050a0220.31b08.e540@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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).