From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v2,1/3] Bluetooth: HCI: Add HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN quirk
Date: Tue, 29 Mar 2022 14:06:15 -0700 (PDT) [thread overview]
Message-ID: <624374c7.1c69fb81.ab9df.6d55@mx.google.com> (raw)
In-Reply-To: <20220329201646.2296314-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2493 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=627309
---Test result---
Test Summary:
CheckPatch FAIL 2.56 seconds
GitLint PASS 1.51 seconds
SubjectPrefix PASS 1.00 seconds
BuildKernel PASS 42.17 seconds
BuildKernel32 PASS 37.86 seconds
Incremental Build with patchesPASS 66.78 seconds
TestRunner: Setup PASS 637.22 seconds
TestRunner: l2cap-tester PASS 19.72 seconds
TestRunner: bnep-tester PASS 8.15 seconds
TestRunner: mgmt-tester PASS 133.25 seconds
TestRunner: rfcomm-tester PASS 10.46 seconds
TestRunner: sco-tester PASS 10.34 seconds
TestRunner: smp-tester PASS 10.30 seconds
TestRunner: userchan-tester PASS 8.39 seconds
Details
##############################
Test: CheckPatch - FAIL - 2.56 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
[v2,2/3] Bluetooth: Print broken quirks\WARNING:SPLIT_STRING: quoted string split across lines
#113: FILE: net/bluetooth/hci_sync.c:3842:
+ "HCI Delete Stored Link Key command is advertised, "
+ "but not supported."),
WARNING:SPLIT_STRING: quoted string split across lines
#116: FILE: net/bluetooth/hci_sync.c:3845:
+ "HCI Read Default Erroneous Data Reporting command is "
+ "advertised, but not supported."),
WARNING:SPLIT_STRING: quoted string split across lines
#119: FILE: net/bluetooth/hci_sync.c:3848:
+ "HCI Read Transmit Power Level command is advertised, "
+ "but not supported."),
WARNING:SPLIT_STRING: quoted string split across lines
#124: FILE: net/bluetooth/hci_sync.c:3853:
+ "HCI Enhanced Setup Synchronous Connection command is "
+ "advertised, but not supported.")
total: 0 errors, 4 warnings, 0 checks, 78 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/12795219.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-29 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 20:16 [PATCH v2 1/3] Bluetooth: HCI: Add HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN quirk Luiz Augusto von Dentz
2022-03-29 20:16 ` [PATCH v2 2/3] Bluetooth: Print broken quirks Luiz Augusto von Dentz
2022-03-30 6:13 ` Paul Menzel
2022-03-30 18:00 ` Luiz Augusto von Dentz
2022-03-30 11:51 ` Marcel Holtmann
2022-03-29 20:16 ` [PATCH v2 3/3] Bluetooth: btusb: Set HCI_QUIRK_BROKEN_ENHANCED_SETUP_SYNC_CONN for QCA Luiz Augusto von Dentz
2022-03-29 20:26 ` Luiz Augusto von Dentz
2022-03-29 21:06 ` 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=624374c7.1c69fb81.ab9df.6d55@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