From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pip@pipobscure.com
Subject: RE: Don't auto-bond on reactive GATT security elevation
Date: Sat, 18 Jul 2026 14:22:24 -0700 (PDT) [thread overview]
Message-ID: <6a5bee90.92ea0e2a.4a9a5.5b46@mx.google.com> (raw)
In-Reply-To: <20260718194230.35959-2-pip@pipobscure.com>
[-- Attachment #1: Type: text/plain, Size: 2823 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=1130150
---Test result---
Test Summary:
CheckPatch FAIL 0.71 seconds
GitLint PASS 0.46 seconds
BuildEll PASS 18.36 seconds
BluezMake PASS 653.95 seconds
MakeCheck PASS 18.62 seconds
MakeDistcheck PASS 147.18 seconds
CheckValgrind PASS 211.82 seconds
CheckSmatch PASS 248.24 seconds
bluezmakeextell PASS 91.53 seconds
IncrementalBuild PASS 1156.64 seconds
ScanBuild PASS 818.66 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,1/2] shared/att: don't auto-bond on reactive elevation
WARNING:BAD_SIGN_OFF: Non-standard signature: Assisted-by:
#107:
Assisted-by: Claude:Opus-4.8
ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Claude:Opus-4.8'
#107:
Assisted-by: Claude:Opus-4.8
/github/workspace/src/patch/14695485.patch total: 1 errors, 1 warnings, 73 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/14695485.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,2/2] unit/test-gatt: cover no-auto-sec on auth error
WARNING:BAD_SIGN_OFF: Non-standard signature: Assisted-by:
#81:
Assisted-by: Claude:Opus-4.8
ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Claude:Opus-4.8'
#81:
Assisted-by: Claude:Opus-4.8
/github/workspace/src/patch/14695486.patch total: 1 errors, 1 warnings, 46 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/14695486.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.
https://github.com/bluez/bluez/pull/2330
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-07-18 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 19:42 [PATCH BlueZ 0/2] Don't auto-bond on reactive GATT security elevation Philipp Dunkel
2026-07-18 19:42 ` [PATCH BlueZ 1/2] shared/att: don't auto-bond on reactive elevation Philipp Dunkel
2026-07-18 21:22 ` bluez.test.bot [this message]
2026-07-18 19:42 ` [PATCH BlueZ 2/2] unit/test-gatt: cover no-auto-sec on auth error Philipp Dunkel
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=6a5bee90.92ea0e2a.4a9a5.5b46@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pip@pipobscure.com \
/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.