From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [RFC] Bluetooth: don't use ESCO setup for BT_VOICE
Date: Sun, 27 Feb 2022 09:16:41 -0800 (PST) [thread overview]
Message-ID: <621bb1f9.1c69fb81.5f9b2.bd54@mx.google.com> (raw)
In-Reply-To: <20220227163430.24694-1-pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 1303 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=618448
---Test result---
Test Summary:
CheckPatch PASS 2.01 seconds
GitLint FAIL 1.07 seconds
SubjectPrefix PASS 0.86 seconds
BuildKernel PASS 34.67 seconds
BuildKernel32 PASS 30.46 seconds
Incremental Build with patchesPASS 41.73 seconds
TestRunner: Setup PASS 544.79 seconds
TestRunner: l2cap-tester PASS 15.36 seconds
TestRunner: bnep-tester PASS 6.82 seconds
TestRunner: mgmt-tester PASS 119.15 seconds
TestRunner: rfcomm-tester PASS 9.02 seconds
TestRunner: sco-tester PASS 8.56 seconds
TestRunner: smp-tester PASS 8.42 seconds
TestRunner: userchan-tester PASS 7.03 seconds
Details
##############################
Test: GitLint - FAIL - 1.07 seconds
Run gitlint with rule in .gitlint
[RFC] Bluetooth: don't use ESCO setup for BT_VOICE
20: B2 Line has trailing whitespace: " "
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-02-27 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 21:22 [RFC] Bluetooth: SCO: Fix codec when using HCI_Enhanced_Setup_Synchronous_Connection Luiz Augusto von Dentz
2022-02-23 2:55 ` kernel test robot
2022-02-24 13:42 ` Marcel Holtmann
2022-02-27 16:34 ` [RFC] Bluetooth: don't use ESCO setup for BT_VOICE Pauli Virtanen
2022-02-27 17:16 ` bluez.test.bot [this message]
2022-02-27 17:36 ` 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=621bb1f9.1c69fb81.5f9b2.bd54@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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.