From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, wangyouwan@uniontech.com
Subject: RE: device: Fix timeout=1 to remove the device immediately
Date: Tue, 21 Jun 2022 08:21:18 -0700 (PDT) [thread overview]
Message-ID: <62b1e1ee.1c69fb81.1dd09.5d50@mx.google.com> (raw)
In-Reply-To: <20220621134818.11515-1-wangyouwan@uniontech.com>
[-- Attachment #1: Type: text/plain, Size: 1326 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=652390
---Test result---
Test Summary:
CheckPatch PASS 1.46 seconds
GitLint FAIL 0.99 seconds
Prep - Setup ELL PASS 39.86 seconds
Build - Prep PASS 0.65 seconds
Build - Configure PASS 7.75 seconds
Build - Make PASS 1297.39 seconds
Make Check PASS 11.36 seconds
Make Check w/Valgrind PASS 403.84 seconds
Make Distcheck PASS 216.05 seconds
Build w/ext ELL - Configure PASS 8.26 seconds
Build w/ext ELL - Make PASS 1309.01 seconds
Incremental Build with patchesPASS 0.00 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
device: Fix timeout=1 to remove the device immediately
9: B3 Line contains hard tab characters (\t): " if (!timeout)"
10: B3 Line contains hard tab characters (\t): " return;"
13: B2 Line has trailing whitespace: " "
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-06-21 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 13:48 [PATCH] device: Fix timeout=1 to remove the device immediately Youwan Wang
2022-06-21 15:21 ` bluez.test.bot [this message]
2022-06-21 18:39 ` Luiz Augusto von Dentz
[not found] ` <tencent_6B5C18C2035497666D06DB0C@qq.com>
2022-06-22 20:07 ` Luiz Augusto von Dentz
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=62b1e1ee.1c69fb81.1dd09.5d50@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=wangyouwan@uniontech.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).