From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, devnull+j.jannau.net@kernel.org
Subject: RE: Bluetooth: hci_bcm4377: Mark bcm4378/bcm4387 as BROKEN_LE_CODED
Date: Mon, 16 Oct 2023 01:01:58 -0700 (PDT) [thread overview]
Message-ID: <652cedf6.c80a0220.ea061.a845@mx.google.com> (raw)
In-Reply-To: <20231016-bt-bcm4377-quirk-broken-le-coded-v1-1-52ea69d3c979@jannau.net>
[-- Attachment #1: Type: text/plain, Size: 2076 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=793415
---Test result---
Test Summary:
CheckPatch PASS 0.69 seconds
GitLint FAIL 0.55 seconds
SubjectPrefix PASS 0.12 seconds
BuildKernel PASS 35.57 seconds
CheckAllWarning PASS 39.05 seconds
CheckSparse PASS 46.12 seconds
CheckSmatch PASS 122.79 seconds
BuildKernel32 PASS 32.30 seconds
TestRunnerSetup PASS 511.24 seconds
TestRunner_l2cap-tester PASS 29.67 seconds
TestRunner_iso-tester PASS 54.02 seconds
TestRunner_bnep-tester PASS 9.81 seconds
TestRunner_mgmt-tester PASS 210.52 seconds
TestRunner_rfcomm-tester PASS 15.10 seconds
TestRunner_sco-tester PASS 18.68 seconds
TestRunner_ioctl-tester PASS 17.14 seconds
TestRunner_mesh-tester PASS 12.68 seconds
TestRunner_smp-tester PASS 13.53 seconds
TestRunner_userchan-tester PASS 10.35 seconds
IncrementalBuild PASS 31.09 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: hci_bcm4377: Mark bcm4378/bcm4387 as BROKEN_LE_CODED
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
11: B1 Line exceeds max length (96>80): "Link: https://discussion.fedoraproject.org/t/mx-master-3-bluetooth-mouse-doesnt-connect/87072/33"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-10-16 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 7:13 [PATCH] Bluetooth: hci_bcm4377: Mark bcm4378/bcm4387 as BROKEN_LE_CODED Janne Grunau via B4 Relay
2023-10-16 7:13 ` Janne Grunau via B4 Relay
2023-10-16 7:13 ` Janne Grunau
2023-10-16 8:01 ` bluez.test.bot [this message]
2023-10-16 10:21 ` Eric Curtin
2023-10-16 10:21 ` Eric Curtin
2023-10-16 16:03 ` Neal Gompa
2023-10-16 16:03 ` Neal Gompa
2023-10-16 17:40 ` patchwork-bot+bluetooth
2023-10-16 17:40 ` patchwork-bot+bluetooth
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=652cedf6.c80a0220.ea061.a845@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=devnull+j.jannau.net@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.