From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: longli@linuxonhyperv.com
Subject: |WARNING| pw113604 [PATCH 01/17] net/mana: add basic driver, build environment and doc
Date: Fri, 1 Jul 2022 11:03:47 +0200 (CEST) [thread overview]
Message-ID: <20220701090347.92B4A120787@dpdk.org> (raw)
In-Reply-To: <1656666167-26035-2-git-send-email-longli@linuxonhyperv.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/113604
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#55:
MANA is a PCI device. It uses IB verbs to access hardware through the kernel
WARNING:TYPO_SPELLING: 'Adatper' may be misspelled - perhaps 'Adapter'?
#138: FILE: doc/guides/nics/mana.rst:8:
+for Microsoft Azure Network Adatper VF in SR-IOV context.
WARNING:TYPO_SPELLING: 'Adatper' may be misspelled - perhaps 'Adapter'?
#164: FILE: doc/guides/nics/mana.rst:34:
+ Low-level user space driver library for Microsoft Azure Network Adatper
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'name' - possible side-effects?
#240: FILE: drivers/net/mana/mana.c:50:
+#define MKSTR(name, ...) \
+ int mkstr_size_##name = snprintf(NULL, 0, "" __VA_ARGS__); \
+ char name[mkstr_size_##name + 1]; \
+ \
+ memset(name, 0, mkstr_size_##name + 1); \
+ snprintf(name, sizeof(name), "" __VA_ARGS__)
WARNING:STATIC_CONST_CHAR_ARRAY: static const char * array should probably be static const char * const
#274: FILE: drivers/net/mana/mana.c:84:
+static const char *mana_init_args[] = {
CHECK:CAMELCASE: Avoid CamelCase: <SCNx32>
#428: FILE: drivers/net/mana/mana.c:238:
+ "%" SCNx32 ":%" SCNx8 ":%" SCNx8 ".%" SCNx8 "
",
CHECK:CAMELCASE: Avoid CamelCase: <SCNx8>
#428: FILE: drivers/net/mana/mana.c:238:
+ "%" SCNx32 ":%" SCNx8 ":%" SCNx8 ".%" SCNx8 "
",
total: 0 errors, 4 warnings, 3 checks, 1327 lines checked
parent reply other threads:[~2022-07-01 9:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1656666167-26035-2-git-send-email-longli@linuxonhyperv.com>]
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=20220701090347.92B4A120787@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=longli@linuxonhyperv.com \
--cc=test-report@dpdk.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).