From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1] shared/shell: Allow script command to be used within scripts
Date: Wed, 25 Sep 2024 13:10:36 -0700 (PDT) [thread overview]
Message-ID: <66f46e3c.050a0220.331d63.9a7f@mx.google.com> (raw)
In-Reply-To: <20240925182730.2035299-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2231 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=892874
---Test result---
Test Summary:
CheckPatch FAIL 0.70 seconds
GitLint PASS 0.33 seconds
BuildEll PASS 24.50 seconds
BluezMake PASS 1661.18 seconds
MakeCheck PASS 12.87 seconds
MakeDistcheck PASS 179.47 seconds
CheckValgrind PASS 252.10 seconds
CheckSmatch WARNING 355.16 seconds
bluezmakeextell PASS 118.97 seconds
IncrementalBuild PASS 1505.57 seconds
ScanBuild PASS 1041.24 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v1] shared/shell: Allow script command to be used within scripts
ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#153: FILE: src/shared/shell.c:390:
+ while (bt_shell_input_line(input));
/github/workspace/src/src/13812385.patch total: 1 errors, 0 warnings, 68 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/13812385.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: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):src/shared/shell.c: note: in included file (through /usr/include/readline/readline.h):
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-09-25 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 18:27 [PATCH BlueZ v1] shared/shell: Allow script command to be used within scripts Luiz Augusto von Dentz
2024-09-25 20:10 ` bluez.test.bot [this message]
2024-09-26 19:20 ` 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=66f46e3c.050a0220.331d63.9a7f@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