From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: [BlueZ,1/3] mesh: Remove unused but set variable
Date: Mon, 11 May 2026 07:27:45 -0700 (PDT) [thread overview]
Message-ID: <6a01e761.050a0220.2bd27.9332@mx.google.com> (raw)
In-Reply-To: <20260511113511.1217887-1-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 4068 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=1092724
---Test result---
Test Summary:
CheckPatch FAIL 1.45 seconds
GitLint FAIL 1.04 seconds
BuildEll PASS 20.50 seconds
BluezMake PASS 610.73 seconds
MakeCheck PASS 1.04 seconds
MakeDistcheck PASS 235.67 seconds
CheckValgrind PASS 201.97 seconds
CheckSmatch PASS 322.12 seconds
bluezmakeextell PASS 164.82 seconds
IncrementalBuild PASS 604.45 seconds
ScanBuild PASS 905.83 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,2/3] mesh: Fix str{r,}chr usage
WARNING:LONG_LINE: line length of 82 exceeds 80 columns
#95: FILE: tools/mesh/mesh-db.c:2589:
+ str_s = json_object_to_json_string_ext(expt_cfg, JSON_C_TO_STRING_PRETTY |
/github/workspace/src/patch/14565358.patch total: 0 errors, 1 warnings, 41 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/14565358.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,1/3] mesh: Remove unused but set variable
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 (98>80): "mesh/net.c:1569:18: error: variable ‘ack_copy’ set but not used [-Werror=unused-but-set-variable=]"
[BlueZ,2/3] mesh: Fix str{r,}chr usage
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
8: B1 Line exceeds max length (130>80): "tools/mesh/mesh-db.c:2598:13: error: assignment discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]"
11: B1 Line exceeds max length (130>80): "tools/mesh/mesh-db.c:2604:13: error: assignment discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]"
14: B1 Line exceeds max length (130>80): "tools/mesh/mesh-db.c:2613:13: error: assignment discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]"
[BlueZ,3/3] mesh: Fix const qualifier dropping when using strchr()
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
7: B1 Line exceeds max length (120>80): "mesh/util.c:108:14: error: assignment discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]"
https://github.com/bluez/bluez/pull/2117
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-05-11 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 11:35 [BlueZ 1/3] mesh: Remove unused but set variable Bastien Nocera
2026-05-11 11:35 ` [BlueZ 2/3] mesh: Fix str{r,}chr usage Bastien Nocera
2026-05-11 11:35 ` [BlueZ 3/3] mesh: Fix const qualifier dropping when using strchr() Bastien Nocera
2026-05-11 14:27 ` bluez.test.bot [this message]
2026-05-12 19:20 ` [BlueZ 1/3] mesh: Remove unused but set variable 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=6a01e761.050a0220.2bd27.9332@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