From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, michaelfsun@google.com
Subject: RE: [bluez,v1,1/3] btmgmt: Add btmgmt command advmon-features
Date: Mon, 15 Jun 2020 17:12:25 -0700 (PDT) [thread overview]
Message-ID: <5ee80e69.1c69fb81.137a4.8518@mx.google.com> (raw)
In-Reply-To: <20200616000318.42664-2-michaelfsun@google.com>
[-- Attachment #1: Type: text/plain, Size: 1198 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:STATIC_CONST_CHAR_ARRAY: static const char * array should probably be static const char * const
#25: FILE: tools/btmgmt.c:4570:
+static const char *advmon_features_str[] = {
WARNING:BRACES: braces {} are not necessary for single statement blocks
#81: FILE: tools/btmgmt.c:4626:
+ for (i = 0; i < num_handles; i++) {
+ print("\t0x%04x ", le16_to_cpu(rp->handles[i]));
+ }
- total: 0 errors, 2 warnings, 93 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
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-06-16 0:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 0:03 [bluez PATCH v1 0/3] Add new commands in btmgmt to support adv monitor Michael Sun
2020-06-16 0:03 ` [bluez PATCH v1 1/3] btmgmt: Add btmgmt command advmon-features Michael Sun
2020-06-16 0:12 ` bluez.test.bot [this message]
2020-06-16 0:13 ` Add new commands in btmgmt to support adv monitor bluez.test.bot
2020-06-16 1:34 ` [bluez PATCH v1 1/3] btmgmt: Add btmgmt command advmon-features Von Dentz, Luiz
2020-06-16 0:03 ` [bluez PATCH v1 2/3] btmgmt: Add btmgmt command advmon-remove Michael Sun
2020-06-16 0:12 ` [bluez,v1,2/3] " bluez.test.bot
2020-06-16 0:03 ` [bluez PATCH v1 3/3] btmgmt: Add btmgmt command advmon-add Michael Sun
2020-06-16 0:12 ` [bluez,v1,3/3] " 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=5ee80e69.1c69fb81.137a4.8518@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michaelfsun@google.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).