From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v3,1/3] Bluetooth: HCI: Add HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN quirk
Date: Wed, 30 Mar 2022 12:10:37 -0700 (PDT) [thread overview]
Message-ID: <6244ab2d.1c69fb81.a264e.2415@mx.google.com> (raw)
In-Reply-To: <20220330182552.2613523-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2490 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=627595
---Test result---
Test Summary:
CheckPatch FAIL 3.86 seconds
GitLint PASS 3.01 seconds
SubjectPrefix PASS 2.73 seconds
BuildKernel PASS 35.53 seconds
BuildKernel32 PASS 31.77 seconds
Incremental Build with patchesPASS 57.23 seconds
TestRunner: Setup PASS 520.37 seconds
TestRunner: l2cap-tester PASS 16.62 seconds
TestRunner: bnep-tester PASS 6.67 seconds
TestRunner: mgmt-tester PASS 107.83 seconds
TestRunner: rfcomm-tester PASS 8.50 seconds
TestRunner: sco-tester PASS 8.32 seconds
TestRunner: smp-tester PASS 8.34 seconds
TestRunner: userchan-tester PASS 6.95 seconds
Details
##############################
Test: CheckPatch - FAIL - 3.86 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
[v3,2/3] Bluetooth: Print broken quirks\WARNING:SPLIT_STRING: quoted string split across lines
#109: FILE: net/bluetooth/hci_sync.c:3838:
+ "HCI Delete Stored Link Key command is advertised, "
+ "but not supported."),
WARNING:SPLIT_STRING: quoted string split across lines
#112: FILE: net/bluetooth/hci_sync.c:3841:
+ "HCI Read Default Erroneous Data Reporting command is "
+ "advertised, but not supported."),
WARNING:SPLIT_STRING: quoted string split across lines
#115: FILE: net/bluetooth/hci_sync.c:3844:
+ "HCI Read Transmit Power Level command is advertised, "
+ "but not supported."),
WARNING:SPLIT_STRING: quoted string split across lines
#120: FILE: net/bluetooth/hci_sync.c:3849:
+ "HCI Enhanced Setup Synchronous Connection command is "
+ "advertised, but not supported.")
total: 0 errors, 4 warnings, 0 checks, 65 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/12796216.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.
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2022-03-30 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 18:25 [PATCH v3 1/3] Bluetooth: HCI: Add HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN quirk Luiz Augusto von Dentz
2022-03-30 18:25 ` [PATCH v3 2/3] Bluetooth: Print broken quirks Luiz Augusto von Dentz
2022-04-01 17:29 ` Marcel Holtmann
2022-04-01 21:01 ` Luiz Augusto von Dentz
2022-03-30 18:25 ` [PATCH v3 3/3] Bluetooth: btusb: Set HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN for QCA Luiz Augusto von Dentz
2022-04-01 17:30 ` Marcel Holtmann
2022-04-01 21:05 ` Luiz Augusto von Dentz
2022-03-30 19:10 ` 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=6244ab2d.1c69fb81.a264e.2415@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).