From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: "cleanup" variable attribute follow-up
Date: Tue, 09 Jun 2026 10:30:16 -0700 (PDT) [thread overview]
Message-ID: <6a284da8.7dd3efdf.a331b.6852@mx.google.com> (raw)
In-Reply-To: <20260609135837.476561-2-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 4250 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=1108616
---Test result---
Test Summary:
CheckPatch FAIL 2.51 seconds
GitLint PASS 1.73 seconds
BuildEll PASS 16.19 seconds
BluezMake PASS 498.81 seconds
MakeCheck PASS 18.30 seconds
MakeDistcheck PASS 189.35 seconds
CheckValgrind PASS 217.95 seconds
CheckSmatch WARNING 253.71 seconds
bluezmakeextell PASS 131.42 seconds
IncrementalBuild PASS 985.31 seconds
ScanBuild PASS 733.50 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,1/6] shared/util: Fix warnings when cleaning up NULL pointers
WARNING:LONG_LINE: line length of 94 exceeds 80 columns
#74: FILE: src/shared/util.h:130:
+ static inline void cleanup_##type (type **_ptr) { if (*_ptr != NULL) (func) (*_ptr); }
WARNING:SPACING: space prohibited between function name and open parenthesis '('
#74: FILE: src/shared/util.h:130:
+ static inline void cleanup_##type (type **_ptr) { if (*_ptr != NULL) (func) (*_ptr); }
ERROR:SPACING: need consistent spacing around '*' (ctx:WxO)
#74: FILE: src/shared/util.h:130:
+ static inline void cleanup_##type (type **_ptr) { if (*_ptr != NULL) (func) (*_ptr); }
^
ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#74: FILE: src/shared/util.h:130:
+ static inline void cleanup_##type (type **_ptr) { if (*_ptr != NULL) (func) (*_ptr); }
/github/workspace/src/patch/14619750.patch total: 2 errors, 2 warnings, 8 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/patch/14619750.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,4/6] main: Use _cleanup_() to simplify configuration parsing
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#90: FILE: src/main.c:265:
+ _cleanup_type_(GError) GError *err = NULL;
^
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#114: FILE: src/main.c:447:
+ _cleanup_type_(GError) GError *err = NULL;
^
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#210: FILE: src/main.c:895:
+ _cleanup_type_(GError) GError *err = NULL;
^
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#415: FILE: src/main.c:1214:
+ _cleanup_type_(GError) GError *err = NULL;
^
ERROR:SPACING: need consistent spacing around '*' (ctx:WxV)
#507: FILE: src/main.c:1577:
+ _cleanup_type_(GError) GError *err = NULL;
^
/github/workspace/src/patch/14619699.patch total: 5 errors, 0 warnings, 420 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/patch/14619699.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):
https://github.com/bluez/bluez/pull/2201
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-06-09 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 13:50 [BlueZ 0/6] "cleanup" variable attribute follow-up Bastien Nocera
2026-06-09 13:50 ` [BlueZ 1/6] shared/util: Fix warnings when cleaning up NULL pointers Bastien Nocera
2026-06-09 17:30 ` bluez.test.bot [this message]
2026-06-09 13:50 ` [BlueZ 2/6] shared/util: Better type-checking in _steal_* commands Bastien Nocera
2026-06-09 13:50 ` [BlueZ 3/6] doc: Recommend using _cleanup_ and friends Bastien Nocera
2026-06-09 13:50 ` [BlueZ 4/6] main: Use _cleanup_() to simplify configuration parsing Bastien Nocera
2026-06-09 13:50 ` [BlueZ 5/6] client: Use _cleanup_fd_ to simplify urandom access Bastien Nocera
2026-06-09 13:50 ` [BlueZ 6/6] btattach: Use _cleanup_fd_ to simplify error paths Bastien Nocera
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=6a284da8.7dd3efdf.a331b.6852@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