From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hdegoede@redhat.com
Subject: RE: Bluetooth: btusb: 2 fixes for handling of fake CSR USB dongles
Date: Mon, 23 Nov 2020 03:04:35 -0800 (PST) [thread overview]
Message-ID: <5fbb9743.1c69fb81.0713.4361@mx.google.com> (raw)
In-Reply-To: <20201123101308.7291-2-hdegoede@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1100 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=389341
---Test result---
##############################
Test: CheckPatch - PASS
##############################
Test: CheckGitLint - FAIL
Output:
Bluetooth: btusb: Fix detection of some fake CSR controllers with a bcdDevice val of 0x0134
1: T1 Title exceeds max length (91>72): "Bluetooth: btusb: Fix detection of some fake CSR controllers with a bcdDevice val of 0x0134"
17: B1 Line exceeds max length (98>80): "Fixes: cde1a8a99287 ("Bluetooth: btusb: Fix and detect most of the Chinese Bluetooth controllers")"
Bluetooth: btusb: Add workaround for remote-wakeup issues with some fake CSR controllers
1: T1 Title exceeds max length (88>72): "Bluetooth: btusb: Add workaround for remote-wakeup issues with some fake CSR controllers"
##############################
Test: CheckBuildK - PASS
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2020-11-23 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 10:13 [PATCH v2 0/2] Bluetooth: btusb: 2 fixes for handling of fake CSR USB dongles Hans de Goede
2020-11-23 10:13 ` [PATCH v2 1/2] Bluetooth: btusb: Fix detection of some fake CSR controllers with a bcdDevice val of 0x0134 Hans de Goede
2020-11-23 11:04 ` bluez.test.bot [this message]
2020-11-23 10:13 ` [PATCH v2 2/2] Bluetooth: btusb: Add workaround for remote-wakeup issues with some fake CSR controllers Hans de Goede
2020-11-23 10:22 ` Hans de Goede
2020-12-03 13:23 ` Marcel Holtmann
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=5fbb9743.1c69fb81.0713.4361@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hdegoede@redhat.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 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.