From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, raj.khem@gmail.com
Subject: RE: [BlueZ] Provide GNU basename compatible implementation
Date: Mon, 26 Aug 2024 12:50:12 -0700 (PDT) [thread overview]
Message-ID: <66ccdc74.c80a0220.28bdce.0c6a@mx.google.com> (raw)
In-Reply-To: <20240826173844.2918630-1-raj.khem@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2046 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=883477
---Test result---
Test Summary:
CheckPatch FAIL 0.70 seconds
GitLint PASS 0.32 seconds
BuildEll PASS 26.71 seconds
BluezMake PASS 1798.43 seconds
MakeCheck PASS 13.94 seconds
MakeDistcheck PASS 181.55 seconds
CheckValgrind PASS 254.32 seconds
CheckSmatch WARNING 361.88 seconds
bluezmakeextell PASS 126.18 seconds
IncrementalBuild PASS 1520.24 seconds
ScanBuild PASS 1079.55 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ] Provide GNU basename compatible implementation
WARNING:LINE_SPACING: Missing a blank line after declarations
#194: FILE: src/shared/util.h:303:
+ const char *base = strrchr(path, '/');
+ return base ? base + 1 : path;
/github/workspace/src/src/13778304.patch total: 0 errors, 1 warnings, 79 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/13778304.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:
tools/hex2hcd.c:136:26: warning: Variable length array is used.
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2024-08-26 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 17:38 [PATCH BlueZ] Provide GNU basename compatible implementation Khem Raj
2024-08-26 19:50 ` 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=66ccdc74.c80a0220.28bdce.0c6a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=raj.khem@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