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 14:28:00 -0700 (PDT) [thread overview]
Message-ID: <69fbb260.050a0220.817c9.8220@mx.google.com> (raw)
In-Reply-To: <20260506143220.3076135-2-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 1922 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=1090532
---Test result---
Test Summary:
CheckPatch PASS 2.00 seconds
GitLint PASS 1.32 seconds
BuildEll PASS 21.42 seconds
BluezMake PASS 638.21 seconds
MakeCheck PASS 18.99 seconds
MakeDistcheck PASS 232.55 seconds
CheckValgrind PASS 272.18 seconds
CheckSmatch WARNING 331.14 seconds
bluezmakeextell PASS 163.78 seconds
IncrementalBuild PASS 1203.38 seconds
ScanBuild PASS 924.01 seconds
Details
##############################
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/2102
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-05-06 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 14:30 [BlueZ v2 0/5] Add helper for "cleanup" variable attribute Bastien Nocera
2026-05-06 14:30 ` [BlueZ v2 1/5] all: Remove more unneeded MIN/MAX macro definition Bastien Nocera
2026-05-06 21:28 ` bluez.test.bot [this message]
2026-05-06 14:30 ` [BlueZ v2 2/5] shared/util: Add helper for "cleanup" variable attribute Bastien Nocera
2026-05-06 14:30 ` [BlueZ v2 3/5] doc: Recommend using _cleanup_ and friends Bastien Nocera
2026-05-06 14:30 ` [BlueZ v2 4/5] main: Use _cleanup_() to simplify configuration parsing Bastien Nocera
2026-05-06 14:30 ` [BlueZ v2 5/5] main: Use _cleanup_() to simplify GError-handling Bastien Nocera
2026-05-07 14:42 ` [BlueZ v2 0/5] Add helper for "cleanup" variable attribute Bastien Nocera
-- strict thread matches above, loose matches on Subject: below --
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
2026-05-06 9:14 [BlueZ 1/5] all: Remove more unneeded MIN/MAX macro definition Bastien Nocera
2026-05-06 11:15 ` 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=69fbb260.050a0220.817c9.8220@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