From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, proxy-alt@proxy-alt.dev
Subject: RE: [BlueZ,v2] shared/gatt-client: confirm a synthesized CCC handle before writing to it
Date: Fri, 04 Sep 2026 13:13:14 -0700 (PDT) [thread overview]
Message-ID: <6a9b265a.7eadad10.3238c.1722@mx.google.com> (raw)
In-Reply-To: <20260904182833.59624-1-proxy-alt@proxy-alt.dev>
[-- Attachment #1: Type: text/plain, Size: 2991 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=1158295
---Test result---
Test Summary:
CheckPatch FAIL 0.48 seconds
GitLint FAIL 0.25 seconds
BuildEll PASS 20.07 seconds
BluezMake PASS 549.72 seconds
MakeCheck PASS 1.08 seconds
MakeDistcheck FAIL 127.88 seconds
CheckValgrind PASS 151.27 seconds
CheckSmatch PASS 297.92 seconds
bluezmakeextell PASS 96.93 seconds
IncrementalBuild PASS 562.30 seconds
ScanBuild PASS 878.13 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v2] shared/gatt-client: confirm a synthesized CCC handle before writing to it
WARNING:LONG_LINE: line length of 84 exceeds 80 columns
#251: FILE: src/shared/gatt-client.c:850:
+ queue_push_tail(root_client(client)->unverified_ccc,
WARNING:LONG_LINE: line length of 81 exceeds 80 columns
#270: FILE: src/shared/gatt-client.c:1820:
+ !notify_data->callback) {
/github/workspace/src/patch/14792115.patch total: 0 errors, 2 warnings, 255 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/14792115.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,v2] shared/gatt-client: confirm a synthesized CCC handle before writing to it
1: T1 Title exceeds max length (84>80): "[BlueZ,v2] shared/gatt-client: confirm a synthesized CCC handle before writing to it"
##############################
Test: MakeDistcheck - FAIL
Desc: Run Bluez Make Distcheck
Output:
../../test-driver: line 107: 53187 Aborted (core dumped) "$@" > $log_file 2>&1
../../test-driver: line 107: 53223 Aborted (core dumped) "$@" > $log_file 2>&1
../../test-driver: line 107: 53503 Aborted (core dumped) "$@" > $log_file 2>&1
make[4]: *** [Makefile:10413: test-suite.log] Error 1
make[3]: *** [Makefile:10521: check-TESTS] Error 2
make[2]: *** [Makefile:11006: check-am] Error 2
make[1]: *** [Makefile:11008: check] Error 2
make: *** [Makefile:10929: distcheck] Error 1
https://github.com/bluez/bluez/pull/2493
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-04 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 18:28 [PATCH BlueZ v2] shared/gatt-client: confirm a synthesized CCC handle before writing to it Proxy alt
2026-09-04 20:13 ` bluez.test.bot [this message]
2026-09-04 21:36 ` [PATCH BlueZ v3 1/2] shared/gatt-client: verify a synthesized CCC before writing Proxy alt
2026-09-04 21:36 ` [PATCH BlueZ v3 2/2] unit/test-micp: expect the FIND_INFORMATION the CCC fix adds Proxy alt
2026-09-04 23:47 ` [BlueZ,v3,1/2] shared/gatt-client: verify a synthesized CCC before writing bluez.test.bot
-- strict thread matches above, loose matches on Subject: below --
2026-09-04 16:21 [PATCH BlueZ v2] shared/gatt-client: confirm a synthesized CCC handle before writing to it Proxy alt
2026-09-04 17:07 ` [BlueZ,v2] " 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=6a9b265a.7eadad10.3238c.1722@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=proxy-alt@proxy-alt.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.