From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw39498 [PATCH v6 2/4] net/netvsc: add hyper-v netvsc network device
Date: Wed, 9 May 2018 02:28:00 +0200 (CEST) [thread overview]
Message-ID: <20180509002800.9B2847D0E@dpdk.org> (raw)
In-Reply-To: <20180509002605.30996-3-stephen@networkplumber.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/39498
_coding style issues_
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#63: FILE: MAINTAINERS:576:
+M: Stephen Hemminger <sthemmin@microsoft.com>
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#64: FILE: MAINTAINERS:577:
+M: "K. Y. Srinivasan" <kys@microsoft.com>
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#65: FILE: MAINTAINERS:578:
+M: Haiyang Zhang <haiyangz@microsoft.com>
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#66: FILE: MAINTAINERS:579:
+F: drivers/net/hyperv/
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#67: FILE: MAINTAINERS:580:
+F: doc/guides/nics/netvsc.rst
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#68: FILE: MAINTAINERS:581:
+F: doc/guides/nics/features/netvsc.ini
CHECK:CAMELCASE: Avoid CamelCase: <PRIx64>
#438: FILE: drivers/net/netvsc/hn_ethdev.c:299:
+ "unsupported TX offload: %#" PRIx64,
CHECK:CAMELCASE: Avoid CamelCase: <PRIx32>
#2422: FILE: drivers/net/netvsc/hn_rndis.c:720:
+ PMD_DRV_LOG(ERR, "exec RNDIS set %#" PRIx32 " failed",
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'ofs' - possible side-effects?
#3364: FILE: drivers/net/netvsc/hn_rxtx.c:525:
+#define IS_OFFSET_INVALID(ofs) \
+ ((ofs) < RNDIS_PACKET_MSG_OFFSET_MIN || \
+ ((ofs) & RNDIS_PACKET_MSG_OFFSET_ALIGNMASK))
total: 0 errors, 6 warnings, 4887 lines checked
parent reply other threads:[~2018-05-09 0:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180509002605.30996-3-stephen@networkplumber.org>]
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=20180509002800.9B2847D0E@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=stephen@networkplumber.org \
--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).