From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v2] a2dp: Fix handling of codec capability storage
Date: Mon, 22 Jun 2026 11:14:51 -0700 (PDT) [thread overview]
Message-ID: <6a397b9b.ce53cff3.1780fc.6273@mx.google.com> (raw)
In-Reply-To: <20260622155621.675255-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2377 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=1114843
---Test result---
Test Summary:
CheckPatch FAIL 0.92 seconds
GitLint FAIL 0.67 seconds
BuildEll PASS 20.21 seconds
BluezMake PASS 619.69 seconds
MakeCheck PASS 3.14 seconds
MakeDistcheck PASS 237.22 seconds
CheckValgrind PASS 206.49 seconds
CheckSmatch PASS 328.16 seconds
bluezmakeextell PASS 166.29 seconds
IncrementalBuild PASS 623.46 seconds
ScanBuild PASS 931.40 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v2] a2dp: Fix handling of codec capability storage
WARNING:BAD_SIGN_OFF: Use a single space after Reported-by:
#101:
Reported-by: p0her (_@p0her_) in TeamH4C working with TrendAI Zero Day Initiative
ERROR:BAD_SIGN_OFF: Unrecognized email address: 'p0her (_@p0her_) in TeamH4C working with TrendAI Zero Day Initiative'
#101:
Reported-by: p0her (_@p0her_) in TeamH4C working with TrendAI Zero Day Initiative
/github/workspace/src/patch/14639629.patch total: 1 errors, 1 warnings, 36 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/14639629.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] a2dp: Fix handling of codec capability storage
9: B1 Line exceeds max length (82>80): "Reported-by: p0her (_@p0her_) in TeamH4C working with TrendAI Zero Day Initiative"
https://github.com/bluez/bluez/pull/2251
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-06-22 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 15:56 [PATCH BlueZ v2] a2dp: Fix handling of codec capability storage Luiz Augusto von Dentz
2026-06-22 18:14 ` bluez.test.bot [this message]
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=6a397b9b.ce53cff3.1780fc.6273@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