From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, stephan.gerhold@kernkonzept.com
Subject: RE: [v2] Bluetooth: btqcomsmd: Fix command timeout after setting BD address
Date: Thu, 16 Jun 2022 03:06:24 -0700 (PDT) [thread overview]
Message-ID: <62ab00a0.1c69fb81.285a1.1af2@mx.google.com> (raw)
In-Reply-To: <20220616093936.1294824-1-stephan.gerhold@kernkonzept.com>
[-- Attachment #1: Type: text/plain, Size: 1428 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=650946
---Test result---
Test Summary:
CheckPatch PASS 0.90 seconds
GitLint FAIL 0.47 seconds
SubjectPrefix PASS 0.35 seconds
BuildKernel PASS 36.72 seconds
BuildKernel32 PASS 33.63 seconds
Incremental Build with patchesPASS 45.84 seconds
TestRunner: Setup PASS 577.07 seconds
TestRunner: l2cap-tester PASS 19.73 seconds
TestRunner: bnep-tester PASS 6.61 seconds
TestRunner: mgmt-tester PASS 118.63 seconds
TestRunner: rfcomm-tester PASS 11.13 seconds
TestRunner: sco-tester PASS 10.79 seconds
TestRunner: smp-tester PASS 10.38 seconds
TestRunner: userchan-tester PASS 7.18 seconds
Details
##############################
Test: GitLint - FAIL - 0.47 seconds
Run gitlint with rule in .gitlint
[v2] Bluetooth: btqcomsmd: Fix command timeout after setting BD address
32: B1 Line exceeds max length (101>80): "v1: https://lore.kernel.org/linux-bluetooth/20220613110745.3778356-1-stephan.gerhold@kernkonzept.com/"
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2022-06-16 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 9:39 [PATCH v2] Bluetooth: btqcomsmd: Fix command timeout after setting BD address Stephan Gerhold
2022-06-16 10:06 ` bluez.test.bot [this message]
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=62ab00a0.1c69fb81.285a1.1af2@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=stephan.gerhold@kernkonzept.com \
/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).