From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, cochcoder@proton.me
Subject: RE: shared/gatt-client: Cancel discovery read-by-type requests
Date: Sat, 07 Nov 2026 00:45:43 -0800 (PST) [thread overview]
Message-ID: <6aeee537.1bdc9ea5.2d1556.20a1@mx.google.com> (raw)
In-Reply-To: <20261107065854.2147141-1-cochcoder@proton.me>
[-- Attachment #1: Type: text/plain, Size: 2012 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/series/1204776/
---Test result---
Test Summary:
CheckPatch PASS 0.36 seconds
GitLint PASS 0.77 seconds
BuildEll PASS 15.93 seconds
BluezMake PASS 223.92 seconds
MakeCheck PASS 13.54 seconds
MakeDistcheck PASS 114.67 seconds
CheckValgrind PASS 276.47 seconds
CheckSmatch WARNING 224.41 seconds
bluezmakeextell PASS 73.86 seconds
TestFunctional PASS 959.71 seconds
IncrementalBuild PASS 228.34 seconds
ScanBuild PASS 819.69 seconds
Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
src/shared/gatt-helpers.c:764:31: warning: Variable length array is used.src/shared/gatt-helpers.c:842:31: warning: Variable length array is used.src/shared/gatt-helpers.c:1335:31: warning: Variable length array is used.src/shared/gatt-helpers.c:1367:23: warning: Variable length array is used.src/shared/gatt-helpers.c:764:31: warning: Variable length array is used.src/shared/gatt-helpers.c:842:31: warning: Variable length array is used.src/shared/gatt-helpers.c:1335:31: warning: Variable length array is used.src/shared/gatt-helpers.c:1367:23: warning: Variable length array is used.src/shared/gatt-helpers.c:764:31: warning: Variable length array is used.src/shared/gatt-helpers.c:842:31: warning: Variable length array is used.src/shared/gatt-helpers.c:1335:31: warning: Variable length array is used.src/shared/gatt-helpers.c:1367:23: warning: Variable length array is used.
https://github.com/bluez/bluez/pull/2779
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-07 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 6:59 [PATCH] shared/gatt-client: Cancel discovery read-by-type requests Kyle Pepper
2026-11-07 8:45 ` bluez.test.bot [this message]
2026-11-07 20:53 ` Luiz Augusto von Dentz
2026-11-11 21:42 ` [PATCH v2 0/3] shared/gatt-client: Track internal discovery reads Kyle Pepper
2026-11-11 21:43 ` [PATCH v2 1/3] shared/gatt-client: Support pending GATT helper requests Kyle Pepper
2026-11-12 1:58 ` shared/gatt-client: Track internal discovery reads bluez.test.bot
2026-11-11 21:43 ` [PATCH v2 2/3] shared/gatt-client: Track pending Server Features reads Kyle Pepper
2026-11-11 21:44 ` [PATCH v2 3/3] shared/gatt-client: Track pending discovery Database Hash reads Kyle Pepper
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=6aeee537.1bdc9ea5.2d1556.20a1@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=cochcoder@proton.me \
--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