From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: Add helper for "cleanup" variable attribute
Date: Wed, 06 May 2026 04:15:36 -0700 (PDT) [thread overview]
Message-ID: <69fb22d8.050a0220.1d3108.0591@mx.google.com> (raw)
In-Reply-To: <20260506091824.2920716-2-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 4626 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=1090349
---Test result---
Test Summary:
CheckPatch FAIL 1.57 seconds
GitLint PASS 1.32 seconds
BuildEll PASS 20.73 seconds
BluezMake PASS 654.60 seconds
MakeCheck PASS 19.06 seconds
MakeDistcheck PASS 249.78 seconds
CheckValgrind PASS 296.64 seconds
CheckSmatch WARNING 355.15 seconds
bluezmakeextell PASS 184.37 seconds
IncrementalBuild PASS 1277.75 seconds
ScanBuild PASS 1024.24 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,2/5] shared/util: Add helper for "cleanup" variable attribute
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#74: FILE: src/shared/util.h:96:
+static inline void freep(void *p) {
ERROR:CODE_INDENT: code indent should use tabs where possible
#75: FILE: src/shared/util.h:97:
+ free(*(void**) p);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#75: FILE: src/shared/util.h:97:
+ free(*(void**) p);$
ERROR:POINTER_LOCATION: "(foo**)" should be "(foo **)"
#75: FILE: src/shared/util.h:97:
+ free(*(void**) p);
/github/workspace/src/patch/14557019.patch total: 3 errors, 1 warnings, 13 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.
NOTE: Whitespace errors detected.
You may wish to use scripts/cleanpatch or scripts/cleanfile
/github/workspace/src/patch/14557019.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.
[BlueZ,5/5] main: Use _cleanup_() to simplify GError-handling
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#66: FILE: src/main.c:208:
+static inline void free_error(void *err) {
ERROR:CODE_INDENT: code indent should use tabs where possible
#67: FILE: src/main.c:209:
+ g_error_free(*(void**) err);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#67: FILE: src/main.c:209:
+ g_error_free(*(void**) err);$
ERROR:POINTER_LOCATION: "(foo**)" should be "(foo **)"
#67: FILE: src/main.c:209:
+ g_error_free(*(void**) err);
/github/workspace/src/patch/14557018.patch total: 3 errors, 1 warnings, 127 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.
NOTE: Whitespace errors detected.
You may wish to use scripts/cleanpatch or scripts/cleanfile
/github/workspace/src/patch/14557018.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/main.c: note: in included file (through src/device.h):src/shared/gatt-server.c:271:25: warning: Variable length array is used.src/shared/gatt-server.c:614:25: warning: Variable length array is used.src/shared/gatt-server.c:712:25: warning: Variable length array is used.src/shared/gatt-server.c:271:25: warning: Variable length array is used.src/shared/gatt-server.c:614:25: warning: Variable length array is used.src/shared/gatt-server.c:712:25: warning: Variable length array is used.src/shared/gatt-server.c:271:25: warning: Variable length array is used.src/shared/gatt-server.c:614:25: warning: Variable length array is used.src/shared/gatt-server.c:712:25: warning: Variable length array is used.src/main.c: note: in included file (through src/device.h):src/main.c: note: in included file (through src/device.h):
https://github.com/bluez/bluez/pull/2101
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-05-06 11:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 9:14 [BlueZ 0/5] Add helper for "cleanup" variable attribute Bastien Nocera
2026-05-06 9:14 ` [BlueZ 1/5] all: Remove more unneeded MIN/MAX macro definition Bastien Nocera
2026-05-06 11:15 ` bluez.test.bot [this message]
2026-05-06 9:14 ` [BlueZ 2/5] shared/util: Add helper for "cleanup" variable attribute Bastien Nocera
2026-05-06 9:14 ` [BlueZ 3/5] doc: Recommend using _cleanup_ and friends Bastien Nocera
2026-05-06 9:14 ` [BlueZ 4/5] main: Use _cleanup_() to simplify configuration parsing Bastien Nocera
2026-05-06 9:14 ` [BlueZ 5/5] main: Use _cleanup_() to simplify GError-handling Bastien Nocera
-- strict thread matches above, loose matches on Subject: below --
2026-05-06 14:30 [BlueZ v2 1/5] all: Remove more unneeded MIN/MAX macro definition Bastien Nocera
2026-05-06 21:28 ` Add helper for "cleanup" variable attribute bluez.test.bot
2026-05-11 13:18 [BlueZ v3 1/6] all: Remove more unneeded MIN/MAX macro definition Bastien Nocera
2026-05-11 17:27 ` Add helper for "cleanup" variable attribute bluez.test.bot
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=69fb22d8.050a0220.1d3108.0591@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
/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