From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ] configure: Fix use of obsolete macros
Date: Wed, 05 Jan 2022 15:46:06 -0800 (PST) [thread overview]
Message-ID: <61d62dbe.1c69fb81.2987e.0ebf@mx.google.com> (raw)
In-Reply-To: <20220105222946.3235852-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2251 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=603033
---Test result---
Test Summary:
CheckPatch FAIL 1.58 seconds
GitLint FAIL 1.11 seconds
Prep - Setup ELL PASS 43.34 seconds
Build - Prep PASS 0.68 seconds
Build - Configure PASS 8.63 seconds
Build - Make PASS 1436.54 seconds
Make Check PASS 11.94 seconds
Make Check w/Valgrind PASS 451.87 seconds
Make Distcheck PASS 237.29 seconds
Build w/ext ELL - Configure PASS 8.83 seconds
Build w/ext ELL - Make PASS 1406.07 seconds
Incremental Build with patchesPASS 0.00 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[BlueZ] configure: Fix use of obsolete macros
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#86:
https://www.gnu.org/software/autoconf/manual/autoconf-2.70/html_node/Obsolete-Macros.html
/github/workspace/src/12704810.patch total: 0 errors, 1 warnings, 330 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/12704810.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.
##############################
Test: GitLint - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
[BlueZ] configure: Fix use of obsolete macros
13: B1 Line exceeds max length (89>80): "https://www.gnu.org/software/autoconf/manual/autoconf-2.70/html_node/Obsolete-Macros.html"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-01-05 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 22:29 [PATCH BlueZ] configure: Fix use of obsolete macros Luiz Augusto von Dentz
2022-01-05 23:46 ` bluez.test.bot [this message]
2022-01-07 22:44 ` [BlueZ] " 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=61d62dbe.1c69fb81.2987e.0ebf@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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;
as well as URLs for NNTP newsgroup(s).