From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,vRFC,1/4] test-runner: Add support for PCIe passthrough
Date: Thu, 27 Aug 2026 18:17:16 -0700 (PDT) [thread overview]
Message-ID: <6a90e19c.bd0b6004.9a6f6.28e6@mx.google.com> (raw)
In-Reply-To: <20260827165326.350079-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5189 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=1152755
---Test result---
Test Summary:
CheckPatch FAIL 2.19 seconds
GitLint PASS 1.31 seconds
BuildEll PASS 19.97 seconds
BluezMake PASS 541.80 seconds
MakeCheck PASS 19.49 seconds
MakeDistcheck PASS 152.15 seconds
CheckValgrind PASS 220.65 seconds
CheckSmatch WARNING 294.22 seconds
bluezmakeextell PASS 95.10 seconds
IncrementalBuild PASS 590.14 seconds
ScanBuild PASS 866.71 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,vRFC,1/4] test-runner: Add support for PCIe passthrough
WARNING:BAD_SIGN_OFF: Non-standard signature: Assisted-by:
#130:
Assisted-by: Claude:claude-opus-5
ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Claude:claude-opus-5'
#130:
Assisted-by: Claude:claude-opus-5
/github/workspace/src/patch/14771785.patch total: 1 errors, 1 warnings, 431 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/14771785.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,vRFC,2/4] monitor: Add latency standard deviation
WARNING:BAD_SIGN_OFF: Non-standard signature: Assisted-by:
#119:
Assisted-by: opencode:claude-opus-5
ERROR:BAD_SIGN_OFF: Unrecognized email address: 'opencode:claude-opus-5'
#119:
Assisted-by: opencode:claude-opus-5
/github/workspace/src/patch/14771786.patch total: 1 errors, 1 warnings, 107 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/14771786.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,vRFC,3/4] monitor: Add ISO packet loss counters
WARNING:BAD_SIGN_OFF: Non-standard signature: Assisted-by:
#119:
Assisted-by: opencode:claude-opus-5
ERROR:BAD_SIGN_OFF: Unrecognized email address: 'opencode:claude-opus-5'
#119:
Assisted-by: opencode:claude-opus-5
/github/workspace/src/patch/14771787.patch total: 1 errors, 1 warnings, 192 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/14771787.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,vRFC,4/4] doc/btmon: Document the deviation and loss counters
WARNING:BAD_SIGN_OFF: Non-standard signature: Assisted-by:
#110:
Assisted-by: opencode:claude-opus-5
ERROR:BAD_SIGN_OFF: Unrecognized email address: 'opencode:claude-opus-5'
#110:
Assisted-by: opencode:claude-opus-5
/github/workspace/src/patch/14771788.patch total: 1 errors, 1 warnings, 66 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/14771788.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: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/packet.c:2003:26: warning: Variable length array is used.monitor/packet.c: note: in included file:monitor/bt.h:3924:52: warning: array of flexible structuresmonitor/bt.h:3912:40: warning: array of flexible structuresmonitor/packet.c:2003:26: warning: Variable length array is used.monitor/packet.c: note: in included file:monitor/bt.h:3924:52: warning: array of flexible structuresmonitor/bt.h:3912:40: warning: array of flexible structures
https://github.com/bluez/bluez/pull/2444
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-08-28 1:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 16:53 [PATCH BlueZ vRFC 1/4] test-runner: Add support for PCIe passthrough Luiz Augusto von Dentz
2026-08-27 16:53 ` [PATCH BlueZ vRFC 2/4] monitor: Add latency standard deviation Luiz Augusto von Dentz
2026-08-27 16:53 ` [PATCH BlueZ vRFC 3/4] monitor: Add ISO packet loss counters Luiz Augusto von Dentz
2026-08-27 16:53 ` [PATCH BlueZ vRFC 4/4] doc/btmon: Document the deviation and " Luiz Augusto von Dentz
2026-08-28 1:17 ` bluez.test.bot [this message]
2026-09-04 19:30 ` [PATCH BlueZ vRFC 1/4] test-runner: Add support for PCIe passthrough 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=6a90e19c.bd0b6004.9a6f6.28e6@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox