From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, simon.mikuda@streamunlimited.com
Subject: RE: monitor
Date: Thu, 23 Mar 2023 04:48:40 -0700 (PDT) [thread overview]
Message-ID: <641c3c98.370a0220.20fbd.b103@mx.google.com> (raw)
In-Reply-To: <20230323102858.566934-2-simon.mikuda@streamunlimited.com>
[-- Attachment #1: Type: text/plain, Size: 2828 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=733108
---Test result---
Test Summary:
CheckPatch FAIL 1.28 seconds
GitLint FAIL 0.96 seconds
BuildEll PASS 27.11 seconds
BluezMake PASS 867.28 seconds
MakeCheck PASS 11.16 seconds
MakeDistcheck PASS 150.36 seconds
CheckValgrind PASS 245.68 seconds
CheckSmatch WARNING 328.41 seconds
bluezmakeextell PASS 98.55 seconds
IncrementalBuild PASS 1441.30 seconds
ScanBuild PASS 1013.20 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,2/2] monitor: Fix printing Signed Write Command
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#81:
Handle: 0x006f Type: Vendor specific (f7debc9a-7856-3412-7856-341278563412)
/github/workspace/src/src/13185462.patch total: 0 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/src/13185462.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
Output:
[BlueZ,2/2] monitor: Fix printing Signed Write Command
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
6: B1 Line exceeds max length (83>80): " Handle: 0x006f Type: Vendor specific (f7debc9a-7856-3412-7856-341278563412)"
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/att.c: note: in included file:monitor/display.h:82:26: warning: Variable length array is used.monitor/att.c: note: in included file:monitor/display.h:82:26: warning: Variable length array is used.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-03-23 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 10:28 [PATCH BlueZ 0/2] monitor Simon Mikuda
2023-03-23 10:28 ` [PATCH BlueZ 1/2] monitor: Fix crash when there is no write handler Simon Mikuda
2023-03-23 11:48 ` bluez.test.bot [this message]
2023-03-23 10:28 ` [PATCH BlueZ 2/2] monitor: Fix printing Signed Write Command Simon Mikuda
2023-03-23 20:50 ` [PATCH BlueZ 0/2] monitor patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2004-04-27 20:20 monitor dave
2004-04-27 20:34 ` monitor Armen Kaleshian
2004-04-27 21:03 ` monitor Ray Olszewski
2004-04-27 21:34 ` monitor dave
2004-04-28 5:51 ` monitor Richard Adams
2004-04-27 21:15 ` monitor Steven Smith
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=641c3c98.370a0220.20fbd.b103@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=simon.mikuda@streamunlimited.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.