From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, apusaka@google.com
Subject: RE: [Bluez,v4,1/2] audio/transport: change volume to 8bit
Date: Wed, 22 Jul 2020 23:49:24 -0700 (PDT) [thread overview]
Message-ID: <5f1932f4.1c69fb81.79bf5.abb4@mx.google.com> (raw)
In-Reply-To: <20200723142128.Bluez.v4.1.I667fa0ebcc3056a21c22fdaf476a56dd72aff38d@changeid>
[-- Attachment #1: Type: text/plain, Size: 1003 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.
While we are preparing for reviewing the patches, we found the following
issue/warning.
Test Result:
checkpatch Failed
Outputs:
WARNING:SPACING: Unnecessary space before function pointer arguments
#80: FILE: profiles/audio/avrcp.h:97:
+ void (*set_volume) (int8_t volume, struct btd_device *dev,
- total: 0 errors, 1 warnings, 215 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.
Your patch has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED 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:[~2020-07-23 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 6:22 [Bluez PATCH v4 1/2] audio/transport: change volume to 8bit Archie Pusaka
2020-07-23 6:22 ` [Bluez PATCH v4 2/2] audio/transport: supply volume on transport init Archie Pusaka
2020-07-23 6:49 ` bluez.test.bot [this message]
2020-07-23 6:51 ` [Bluez,v4,1/2] audio/transport: change volume to 8bit bluez.test.bot
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=5f1932f4.1c69fb81.79bf5.abb4@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=apusaka@google.com \
--cc=linux-bluetooth@vger.kernel.org \
/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).