From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, sathish.narasimman@intel.com
Subject: RE: [BlueZ,v3,1/3] audio/transport: Adding volume callback to media transport
Date: Tue, 11 Oct 2022 05:36:17 -0700 (PDT) [thread overview]
Message-ID: <63456341.170a0220.a5dde.22a7@mx.google.com> (raw)
In-Reply-To: <20221011113116.70514-1-sathish.narasimman@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2193 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=684476
---Test result---
Test Summary:
CheckPatch FAIL 2.38 seconds
GitLint PASS 1.31 seconds
Prep - Setup ELL PASS 30.54 seconds
Build - Prep PASS 0.78 seconds
Build - Configure PASS 9.45 seconds
Build - Make PASS 1039.19 seconds
Make Check PASS 12.27 seconds
Make Check w/Valgrind PASS 331.94 seconds
Make Distcheck PASS 273.49 seconds
Build w/ext ELL - Configure PASS 9.51 seconds
Build w/ext ELL - Make PASS 99.86 seconds
Incremental Build w/ patches PASS 350.20 seconds
Scan Build PASS 642.82 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[BlueZ,v3,1/3] audio/transport: Adding volume callback to media transport
WARNING:SPACING: Unnecessary space before function pointer arguments
#87: FILE: profiles/audio/transport.c:120:
+ void (*set_volume) (struct media_transport *transp,
WARNING:SPACING: Unnecessary space before function pointer arguments
#89: FILE: profiles/audio/transport.c:122:
+ int8_t (*get_volume) (struct media_transport *transp);
/github/workspace/src/13003868.patch total: 0 errors, 2 warnings, 198 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/13003868.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.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-10-11 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 11:31 [PATCH BlueZ v3 1/3] audio/transport: Adding volume callback to media transport Sathish Narasimman
2022-10-11 11:31 ` [PATCH BlueZ v3 2/3] shared/vcp: Add callback to update media volume Sathish Narasimman
2022-10-11 11:31 ` [PATCH BlueZ v3 3/3] profiles: Register callback function to update volume Sathish Narasimman
2022-10-11 12:36 ` bluez.test.bot [this message]
2022-10-11 19:28 ` [PATCH BlueZ v3 1/3] audio/transport: Adding volume callback to media transport Luiz Augusto von Dentz
2022-10-12 5:42 ` Sathish Narasimman
2022-10-12 19:22 ` Luiz Augusto von Dentz
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=63456341.170a0220.a5dde.22a7@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sathish.narasimman@intel.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;
as well as URLs for NNTP newsgroup(s).