From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hildawu@realtek.com
Subject: RE: [v3] Bluetooth: btusb: Workaround for spotty SCO quality
Date: Wed, 05 Oct 2022 07:02:27 -0700 (PDT) [thread overview]
Message-ID: <633d8e73.050a0220.424a8.1065@mx.google.com> (raw)
In-Reply-To: <20221005124936.2390-1-hildawu@realtek.com>
[-- Attachment #1: Type: text/plain, Size: 2897 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=683218
---Test result---
Test Summary:
CheckPatch PASS 2.07 seconds
GitLint FAIL 1.14 seconds
SubjectPrefix PASS 0.97 seconds
BuildKernel PASS 34.10 seconds
BuildKernel32 PASS 29.76 seconds
Incremental Build with patchesPASS 42.40 seconds
TestRunner: Setup PASS 502.49 seconds
TestRunner: l2cap-tester PASS 17.10 seconds
TestRunner: iso-tester PASS 16.19 seconds
TestRunner: bnep-tester PASS 6.33 seconds
TestRunner: mgmt-tester PASS 103.52 seconds
TestRunner: rfcomm-tester PASS 10.14 seconds
TestRunner: sco-tester PASS 9.48 seconds
TestRunner: ioctl-tester PASS 10.75 seconds
TestRunner: smp-tester PASS 9.54 seconds
TestRunner: userchan-tester PASS 6.58 seconds
Details
##############################
Test: GitLint - FAIL - 1.14 seconds
Run gitlint with rule in .gitlint
[v3] Bluetooth: btusb: Workaround for spotty SCO quality
20: B1 Line exceeds max length (271>80): "23327 ;131.399466000; HCI SCO Data IN ; 0B 00 48 8C A3 55 4F 8A D5 56 E9 35 56 37 8D 55 87 53 55 59 66 D5 57 1D B5 54 00 01 08 AD 00 00 E0 10 00 00 00 85 C6 D5 60 E9 B5 52 94 6D 54 E4 9B 55 B1 B6 D5 62 91 B5 57 84 6D 56 E4 5B 55 75 C6 D5 51 2D B5 53 9A 6D 54 A5 1B;"
21: B1 Line exceeds max length (271>80): "23328 ; 131.399648000; HCI SCO Data OUT ; 0B 00 48 01 C8 AD 00 00 AA DB BA AA A9 72 B4 D9 5D AF 14 53 0C 75 B0 A6 F3 8A 51 B3 54 17 B1 A6 D5 62 C5 D5 6B 35 29 8D C5 1C 56 4C 24 96 9B 8D B5 D7 1A B2 8D BC DA 3B 8C 46 AE 1D 4D A4 04 01 F8 AD 00 00 3D EC BB A9 98 8B 28;"
22: B1 Line exceeds max length (272>80): "23329 ; 131.409467000; HCI SCO Data IN ; 0B 00 48 55 55 C6 D5 62 29 B5 57 B2 6D 54 00 01 38 AD 00 00 E0 10 00 00 00 0B 00 D5 62 55 C6 57 B2 29 B5 00 01 6D 54 00 00 38 AD 00 00 E0 10 00 00 00 92 36 D5 5A ED B5 58 6C 6D 55 B3 1B 55 6B 26 D5 52 D1 B5 54 23 6D 56 82 DB;"
23: B1 Line exceeds max length (271>80): "23330 ; 131.409629000; HCI SCO Data OUT ; 0B 00 48 6D 5B BE DB 89 34 66 E9 FA 99 A6 6E E5 6D 9F 1A 1C 57 D2 66 92 63 98 99 A9 3B 8A 6C 3E 5B 5A 34 A4 96 E2 21 21 8C F8 88 0F 3D E0 52 48 85 18 00 01 08 AD 00 00 0C EB BA A9 A8 28 CA 9A D0 3C 33 45 4A F9 90 FB CA 4B 39;"
24: B1 Line exceeds max length (218>80): "23331 ; 131.429464000; HCI SCO Data IN ; 55 AB 36 D5 48 A9 B5 56 AA 6D 56 D2 DB 55 75 36 D5 56 2D B5 57 5B 6D 54 00 0B 00 48 01 C8 AD 00 00 E0 10 00 00 00 5E C6 D5 56 E1 B5 56 43 6D 55 CA DB 55 7D C6 D5 5B 31 B5;"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-10-05 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 12:49 [PATCH v3] Bluetooth: btusb: Workaround for spotty SCO quality hildawu
2022-10-05 14:02 ` bluez.test.bot [this message]
2022-10-05 14:50 ` Paul Menzel
2022-10-05 18:27 ` Luiz Augusto von Dentz
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=633d8e73.050a0220.424a8.1065@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hildawu@realtek.com \
--cc=linux-bluetooth@vger.kernel.org \
/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).