From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, liumh1@shanghaitech.edu.cn
Subject: RE: ./drivers/bluetooth/btqcomsmd.c: remove superfluous header files from btqcomsmd.c
Date: Tue, 28 Sep 2021 14:05:38 -0700 (PDT) [thread overview]
Message-ID: <615383a2.1c69fb81.b504d.179a@mx.google.com> (raw)
In-Reply-To: <20210928195659.18645-1-liumh1@shanghaitech.edu.cn>
[-- Attachment #1: Type: text/plain, Size: 1954 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=554479
---Test result---
Test Summary:
CheckPatch FAIL 1.60 seconds
GitLint FAIL 0.93 seconds
BuildKernel PASS 702.06 seconds
TestRunner: Setup PASS 506.25 seconds
TestRunner: l2cap-tester PASS 11.37 seconds
TestRunner: bnep-tester PASS 6.01 seconds
TestRunner: mgmt-tester PASS 94.00 seconds
TestRunner: rfcomm-tester PASS 7.34 seconds
TestRunner: sco-tester PASS 7.68 seconds
TestRunner: smp-tester PASS 7.48 seconds
TestRunner: userchan-tester PASS 6.30 seconds
Details
##############################
Test: CheckPatch - FAIL - 1.60 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
./drivers/bluetooth/btqcomsmd.c: remove superfluous header files from btqcomsmd.c\ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 1 errors, 0 warnings, 16 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/12523691.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL - 0.93 seconds
Run gitlint with rule in .gitlint
./drivers/bluetooth/btqcomsmd.c: remove superfluous header files from btqcomsmd.c
1: T1 Title exceeds max length (81>80): "./drivers/bluetooth/btqcomsmd.c: remove superfluous header files from btqcomsmd.c"
---
Regards,
Linux Bluetooth
[-- Attachment #2: l2cap-tester.log --]
[-- Type: application/octet-stream, Size: 51539 bytes --]
[-- Attachment #3: bnep-tester.log --]
[-- Type: application/octet-stream, Size: 3906 bytes --]
[-- Attachment #4: mgmt-tester.log --]
[-- Type: application/octet-stream, Size: 626719 bytes --]
[-- Attachment #5: rfcomm-tester.log --]
[-- Type: application/octet-stream, Size: 14762 bytes --]
[-- Attachment #6: sco-tester.log --]
[-- Type: application/octet-stream, Size: 13921 bytes --]
[-- Attachment #7: smp-tester.log --]
[-- Type: application/octet-stream, Size: 11830 bytes --]
[-- Attachment #8: userchan-tester.log --]
[-- Type: application/octet-stream, Size: 7739 bytes --]
prev parent reply other threads:[~2021-09-28 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 19:56 [PATCH] ./drivers/bluetooth/btqcomsmd.c: remove superfluous header files from btqcomsmd.c Mianhan Liu
2021-09-28 21:05 ` 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=615383a2.1c69fb81.b504d.179a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=liumh1@shanghaitech.edu.cn \
/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).