From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, puffy.taco@gmail.com
Subject: RE: doc/coding-style: Update URL to kernel coding style
Date: Fri, 03 Jun 2022 15:34:58 -0700 (PDT) [thread overview]
Message-ID: <629a8c92.1c69fb81.37f6b.cfd2@mx.google.com> (raw)
In-Reply-To: <20220603212604.13758-1-puffy.taco@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2183 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=647329
---Test result---
Test Summary:
CheckPatch FAIL 1.41 seconds
GitLint PASS 0.96 seconds
Prep - Setup ELL PASS 40.26 seconds
Build - Prep PASS 0.68 seconds
Build - Configure PASS 7.98 seconds
Build - Make PASS 1210.43 seconds
Make Check PASS 11.64 seconds
Make Check w/Valgrind PASS 405.55 seconds
Make Distcheck PASS 222.88 seconds
Build w/ext ELL - Configure PASS 8.39 seconds
Build w/ext ELL - Make PASS 1183.08 seconds
Incremental Build with patchesPASS 0.00 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
doc/coding-style: Update URL to kernel coding style
WARNING:BAD_SIGN_OFF: '-signed-off-by:' is the preferred signature form
#95: FILE: doc/coding-style.txt:9:
-Signed-off-by: line(s)". BlueZ does not used Signed-Off lines, so including
ERROR:BAD_SIGN_OFF: Unrecognized email address: 'line(s)". BlueZ does not used Signed-Off lines, so including'
#95: FILE: doc/coding-style.txt:9:
-Signed-off-by: line(s)". BlueZ does not used Signed-Off lines, so including
/github/workspace/src/12869423.patch total: 1 errors, 1 warnings, 22 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/12869423.patch has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-06-03 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 21:26 [PATCH] doc/coding-style: Update URL to kernel coding style Michael Brudevold
2022-06-03 22:34 ` bluez.test.bot [this message]
2022-06-07 5:41 ` Luiz Augusto von Dentz
2022-06-10 4:20 ` [PATCH] " patchwork-bot+bluetooth
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=629a8c92.1c69fb81.37f6b.cfd2@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=puffy.taco@gmail.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