linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, swyterzone@gmail.com
Subject: RE: Bluetooth: btusb: Make the CSR clone chip force-suspend workaround more generic
Date: Fri, 16 Jul 2021 17:05:28 -0700 (PDT)	[thread overview]
Message-ID: <60f21ec8.1c69fb81.ccb48.9eb4@mx.google.com> (raw)
In-Reply-To: <906e95ce-b0e5-239e-f544-f34d8424c8da@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4768 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=516901

---Test result---

Test Summary:
CheckPatch                    FAIL      0.57 seconds
GitLint                       FAIL      0.13 seconds
BuildKernel                   PASS      606.18 seconds
TestRunner: Setup             PASS      400.30 seconds
TestRunner: l2cap-tester      PASS      2.80 seconds
TestRunner: bnep-tester       PASS      2.11 seconds
TestRunner: mgmt-tester       PASS      30.91 seconds
TestRunner: rfcomm-tester     PASS      2.34 seconds
TestRunner: sco-tester        PASS      2.35 seconds
TestRunner: smp-tester        FAIL      2.32 seconds
TestRunner: userchan-tester   PASS      2.15 seconds

Details
##############################
Test: CheckPatch - FAIL - 0.57 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
Bluetooth: btusb: Make the CSR clone chip force-suspend workaround more generic
WARNING: Unknown commit id '81cac64ba258a', maybe rebased or not pulled?
#21: 
Fixes: 81cac64ba258a ("Bluetooth: Deal with USB devices that are faking CSR vendor")

WARNING: Unknown commit id 'cde1a8a992875', maybe rebased or not pulled?
#22: 
Fixes: cde1a8a992875 ("Bluetooth: btusb: Fix and detect most of the Chinese Bluetooth controllers")

WARNING: Unknown commit id 'd74e0ae7e0303', maybe rebased or not pulled?
#23: 
Fixes: d74e0ae7e0303 ("Bluetooth: btusb: Fix detection of some fake CSR controllers with a bcdDevice val of 0x0134")

WARNING: Unknown commit id '0671c0662383e', maybe rebased or not pulled?
#24: 
Fixes: 0671c0662383e ("Bluetooth: btusb: Add workaround for remote-wakeup issues with Barrot 8041a02 fake CSR controllers")

total: 0 errors, 4 warnings, 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.

"[PATCH] Bluetooth: btusb: Make the CSR clone chip force-suspend" has style problems, please review.

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.


##############################
Test: GitLint - FAIL - 0.13 seconds
Run gitlint with rule in .gitlint
Bluetooth: btusb: Make the CSR clone chip force-suspend workaround more generic
1: T1 Title exceeds max length (79>72): "Bluetooth: btusb: Make the CSR clone chip force-suspend workaround more generic"
17: B1 Line exceeds max length (84>80): "Fixes: 81cac64ba258a ("Bluetooth: Deal with USB devices that are faking CSR vendor")"
18: B1 Line exceeds max length (99>80): "Fixes: cde1a8a992875 ("Bluetooth: btusb: Fix and detect most of the Chinese Bluetooth controllers")"
19: B1 Line exceeds max length (116>80): "Fixes: d74e0ae7e0303 ("Bluetooth: btusb: Fix detection of some fake CSR controllers with a bcdDevice val of 0x0134")"
20: B1 Line exceeds max length (123>80): "Fixes: 0671c0662383e ("Bluetooth: btusb: Add workaround for remote-wakeup issues with Barrot 8041a02 fake CSR controllers")"


##############################
Test: BuildKernel - PASS - 606.18 seconds
Build Kernel with minimal configuration supports Bluetooth


##############################
Test: TestRunner: Setup - PASS - 400.30 seconds
Setup environment for running Test Runner


##############################
Test: TestRunner: l2cap-tester - PASS - 2.80 seconds
Run test-runner with l2cap-tester
Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: bnep-tester - PASS - 2.11 seconds
Run test-runner with bnep-tester
Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: mgmt-tester - PASS - 30.91 seconds
Run test-runner with mgmt-tester
Total: 446, Passed: 443 (99.3%), Failed: 0, Not Run: 3

##############################
Test: TestRunner: rfcomm-tester - PASS - 2.34 seconds
Run test-runner with rfcomm-tester
Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: sco-tester - PASS - 2.35 seconds
Run test-runner with sco-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: smp-tester - FAIL - 2.32 seconds
Run test-runner with smp-tester
Total: 8, Passed: 7 (87.5%), Failed: 1, Not Run: 0

Failed Test Cases
SMP Client - SC Request 2                            Failed       0.024 seconds

##############################
Test: TestRunner: userchan-tester - PASS - 2.15 seconds
Run test-runner with userchan-tester
Total: 3, Passed: 3 (100.0%), Failed: 0, Not Run: 0



---
Regards,
Linux Bluetooth


[-- Attachment #2: l2cap-tester.log --]
[-- Type: application/octet-stream, Size: 44350 bytes --]

[-- Attachment #3: bnep-tester.log --]
[-- Type: application/octet-stream, Size: 3557 bytes --]

[-- Attachment #4: mgmt-tester.log --]
[-- Type: application/octet-stream, Size: 614404 bytes --]

[-- Attachment #5: rfcomm-tester.log --]
[-- Type: application/octet-stream, Size: 11677 bytes --]

[-- Attachment #6: sco-tester.log --]
[-- Type: application/octet-stream, Size: 9912 bytes --]

[-- Attachment #7: smp-tester.log --]
[-- Type: application/octet-stream, Size: 11705 bytes --]

[-- Attachment #8: userchan-tester.log --]
[-- Type: application/octet-stream, Size: 5454 bytes --]

  reply	other threads:[~2021-07-17  0:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16 23:21 [PATCH] Bluetooth: btusb: Make the CSR clone chip force-suspend workaround more generic Ismael Ferreras Morezuelas
2021-07-17  0:05 ` bluez.test.bot [this message]
2021-07-17  9:31 ` Hans de Goede
2021-07-29 19:55 ` Marcel Holtmann
2021-07-29 22:24   ` Ismael Ferreras Morezuelas

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=60f21ec8.1c69fb81.ccb48.9eb4@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=swyterzone@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).