From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_zijuhu@quicinc.com
Subject: RE: Bluetooth: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING
Date: Thu, 21 Jul 2022 00:14:42 -0700 (PDT) [thread overview]
Message-ID: <62d8fce2.1c69fb81.6caeb.05b6@mx.google.com> (raw)
In-Reply-To: <1658383473-32188-2-git-send-email-quic_zijuhu@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 2379 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=661704
---Test result---
Test Summary:
CheckPatch FAIL 1.73 seconds
GitLint FAIL 2.68 seconds
SubjectPrefix PASS 2.42 seconds
BuildKernel PASS 35.75 seconds
BuildKernel32 PASS 31.50 seconds
Incremental Build with patchesPASS 94.85 seconds
TestRunner: Setup PASS 537.66 seconds
TestRunner: l2cap-tester PASS 17.25 seconds
TestRunner: bnep-tester PASS 5.91 seconds
TestRunner: mgmt-tester PASS 99.66 seconds
TestRunner: rfcomm-tester PASS 9.39 seconds
TestRunner: sco-tester PASS 9.13 seconds
TestRunner: smp-tester PASS 9.18 seconds
TestRunner: userchan-tester PASS 6.10 seconds
Details
##############################
Test: CheckPatch - FAIL - 1.73 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
[v2,1/4] Bluetooth: hci_sync: Check LMP feature bit instead of quirk\ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit fatal: unsaf ("ace/src' is owned by someone else)")'
#81:
the quirk was introduced by 'commit cde1a8a99287 ("Bluetooth: btusb: Fix
and detect most of the Chinese Bluetooth controllers")' to mark HCI
total: 1 errors, 0 warnings, 0 checks, 23 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/12924756.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 - 2.68 seconds
Run gitlint with rule in .gitlint
[v2,3/4] Bluetooth: btusb: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING for fake CSR
1: T1 Title exceeds max length (82>80): "[v2,3/4] Bluetooth: btusb: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING for fake CSR"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-07-21 7:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 6:04 [PATCH v2 0/4] Bluetooth: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING Zijun Hu
2022-07-21 6:04 ` [PATCH v2 1/4] Bluetooth: hci_sync: Check LMP feature bit instead of quirk Zijun Hu
2022-07-21 7:14 ` bluez.test.bot [this message]
2022-07-21 6:04 ` [PATCH v2 2/4] Bluetooth: btusb: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING for QCA Zijun Hu
2022-07-21 6:04 ` [PATCH v2 3/4] Bluetooth: btusb: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING for fake CSR Zijun Hu
2022-07-21 6:04 ` [PATCH v2 4/4] Bluetooth: hci_sync: Remove HCI_QUIRK_BROKEN_ERR_DATA_REPORTING Zijun Hu
2022-07-21 16:10 ` [PATCH v2 0/4] Bluetooth: " patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2022-07-20 14:07 [PATCH v1 1/3] Bluetooth: hci_sync: " Zijun Hu
2022-07-20 14:26 ` Bluetooth: " bluez.test.bot
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=62d8fce2.1c69fb81.6caeb.05b6@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=quic_zijuhu@quicinc.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).