From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yang.li@amlogic.com
Subject: RE: [BlueZ,bluez] bap: fixed the return value of GIOFunc
Date: Tue, 28 Jul 2026 22:08:06 -0700 (PDT) [thread overview]
Message-ID: <6a698ab6.d1496011.12e41e.48eb@mx.google.com> (raw)
In-Reply-To: <20260729-fix_iofunc-v1-1-653c8e9ac29a@amlogic.com>
[-- Attachment #1: Type: text/plain, Size: 1996 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=1136288
---Test result---
Test Summary:
CheckPatch FAIL 0.28 seconds
GitLint PASS 0.20 seconds
BuildEll PASS 20.39 seconds
BluezMake PASS 555.77 seconds
MakeCheck PASS 3.19 seconds
MakeDistcheck PASS 159.43 seconds
CheckValgrind PASS 159.91 seconds
CheckSmatch PASS 312.43 seconds
bluezmakeextell PASS 103.33 seconds
IncrementalBuild PASS 563.46 seconds
ScanBuild PASS 984.05 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,bluez] bap: fixed the return value of GIOFunc
WARNING:BAD_FIXES_TAG: Please use correct Fixes: style 'Fixes: <12 chars of sha1> ("<title line>")' - ie: 'Fixes: 322c39a64323 ("bap: Start BIG sync after receiving BIGInfo")'
#77:
Fixes: 322c39a64 (bap: Start BIG sync after receiving BIGInfo)
/github/workspace/src/patch/14717048.patch total: 0 errors, 1 warnings, 18 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/14717048.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/2357
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-07-29 5:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 1:47 [PATCH BlueZ bluez] bap: fixed the return value of GIOFunc Yang Li via B4 Relay
2026-07-29 1:47 ` Yang Li
2026-07-29 5:08 ` bluez.test.bot [this message]
2026-07-29 7:51 ` Bastien Nocera
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=6a698ab6.d1496011.12e41e.48eb@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=yang.li@amlogic.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.