From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-test-report] |WARNING| pw37342 [PATCH 3/3] net/netvsc: add hyper-v netvsc network device
Date: Thu, 5 Apr 2018 21:14:04 +0200 (CEST) [thread overview]
Message-ID: <20180405191404.A83721CDA0@dpdk.org> (raw)
In-Reply-To: <20180405191305.26813-4-sthemmin@microsoft.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/37342
_coding style issues_
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#68: FILE: MAINTAINERS:437:
+M: Stephen Hemminger <sthemmin@microsoft.com>
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#69: FILE: MAINTAINERS:438:
+M: K. Y. Srinivasan" <kys@microsoft.com>
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#70: FILE: MAINTAINERS:439:
+M: Haiyang Zhang <haiyangz@microsoft.com>
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#71: FILE: MAINTAINERS:440:
+F: drivers/net/hyperv/
WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#72: FILE: MAINTAINERS:441:
+F: doc/guides/nics/hyperv.rst
CHECK:CAMELCASE: Avoid CamelCase: <PRIx64>
#553: FILE: drivers/net/netvsc/hn_ethdev.c:316:
+ "unsupported TX offload: %#" PRIx64,
CHECK:CAMELCASE: Avoid CamelCase: <PRIx32>
#2544: FILE: drivers/net/netvsc/hn_rndis.c:721:
+ PMD_DRV_LOG(ERR, "exec RNDIS set %#" PRIx32 " failed",
CHECK:MACRO_ARG_REUSE: Macro argument reuse 'ofs' - possible side-effects?
#3491: FILE: drivers/net/netvsc/hn_rxtx.c:529:
+#define IS_OFFSET_INVALID(ofs) \
+ ((ofs) < RNDIS_PACKET_MSG_OFFSET_MIN || \
+ ((ofs) & RNDIS_PACKET_MSG_OFFSET_ALIGNMASK))
total: 0 errors, 5 warnings, 4988 lines checked
parent reply other threads:[~2018-04-05 19:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180405191305.26813-4-sthemmin@microsoft.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=20180405191404.A83721CDA0@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).