From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hildawu@realtek.com
Subject: RE: Bluetooth: Add btrealtek data struct and improve SCO sound quality of RTK chips
Date: Thu, 29 Sep 2022 05:11:35 -0700 (PDT) [thread overview]
Message-ID: <63358b77.050a0220.c4f70.33b2@mx.google.com> (raw)
In-Reply-To: <20220929114426.4413-2-hildawu@realtek.com>
[-- Attachment #1: Type: text/plain, Size: 2148 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=681879
---Test result---
Test Summary:
CheckPatch PASS 4.94 seconds
GitLint FAIL 2.88 seconds
SubjectPrefix FAIL 1.93 seconds
BuildKernel PASS 44.62 seconds
BuildKernel32 PASS 40.86 seconds
Incremental Build with patchesPASS 75.88 seconds
TestRunner: Setup PASS 694.33 seconds
TestRunner: l2cap-tester PASS 21.50 seconds
TestRunner: iso-tester PASS 22.09 seconds
TestRunner: bnep-tester PASS 8.42 seconds
TestRunner: mgmt-tester PASS 137.38 seconds
TestRunner: rfcomm-tester PASS 13.29 seconds
TestRunner: sco-tester PASS 12.30 seconds
TestRunner: ioctl-tester PASS 14.72 seconds
TestRunner: smp-tester PASS 12.54 seconds
TestRunner: userchan-tester PASS 9.03 seconds
Details
##############################
Test: GitLint - FAIL - 2.88 seconds
Run gitlint with rule in .gitlint
[v3,2/3] Bluetooth: btusb: Workaround for spotty SCO quality
18: B1 Line exceeds max length (85>80): " - Additional info: The comparison of btrtl_usb_recv_isoc here is for invalid handle,"
19: B1 Line exceeds max length (91>80): " the invalid handle shouldn't appear. So we try to find out the rule and filter out this."
[v3,3/3] Bluetooth:btsub:Ignore zero length of USB packets on ALT 6 for specific chip
1: T1 Title exceeds max length (85>80): "[v3,3/3] Bluetooth:btsub:Ignore zero length of USB packets on ALT 6 for specific chip"
15: B1 Line exceeds max length (86>80): " - For ignore_usb_alt6_packet_flow, manage the common flag by the vendor private flag."
##############################
Test: SubjectPrefix - FAIL - 1.93 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-09-29 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 11:44 [PATCH v3 0/3] Bluetooth: Add btrealtek data struct and improve SCO sound quality of RTK chips hildawu
2022-09-29 11:44 ` [PATCH v3 1/3] Bluetooth: btrtl: Add btrealtek data struct hildawu
2022-09-29 12:11 ` bluez.test.bot [this message]
2022-09-29 11:44 ` [PATCH v3 2/3] Bluetooth: btusb: Workaround for spotty SCO quality hildawu
2022-09-29 19:35 ` Luiz Augusto von Dentz
2022-09-29 11:44 ` [PATCH v3 3/3] Bluetooth:btsub:Ignore zero length of USB packets on ALT 6 for specific chip hildawu
-- strict thread matches above, loose matches on Subject: below --
2022-10-05 8:43 [PATCH v4 1/2] Bluetooth: btrtl: Add btrealtek data struct hildawu
2022-10-05 9:19 ` Bluetooth: Add btrealtek data struct and improve SCO sound quality of RTK chips bluez.test.bot
2022-09-13 10:02 [PATCH v2 1/3] Bluetooth: btrtl: Add btrealtek data struct hildawu
2022-09-13 11:11 ` Bluetooth: Add btrealtek data struct and improve SCO sound quality of RTK chips 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=63358b77.050a0220.c4f70.33b2@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).