automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: [dpdk-test-report] |WARNING| pw32366 [PATCH v1 1/3] net/hyperv: introduce MS Hyper-V platform driver
Date: Mon, 18 Dec 2017 17:47:24 +0100 (CET)	[thread overview]
Message-ID: <20171218164724.B331B3250@dpdk.org> (raw)
In-Reply-To: <20171218162443.12971-2-adrien.mazarguil@6wind.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/32366

_coding style issues_


WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#42: FILE: MAINTAINERS:455:
+M: Adrien Mazarguil <adrien.mazarguil@6wind.com>

WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#43: FILE: MAINTAINERS:456:
+F: drivers/net/hyperv/

WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#44: FILE: MAINTAINERS:457:
+F: doc/guides/nics/hyperv.rst

WARNING:MAINTAINERS_STYLE: MAINTAINERS entries use one tab after TYPE:
#45: FILE: MAINTAINERS:458:
+F: doc/guides/nics/features/hyperv.ini

ERROR:SPACING: space required after that ',' (ctx:VxB)
#291: FILE: drivers/net/hyperv/hyperv.c:50:
+		RTE_FMT("%s:%u: %s(): " RTE_FMT_HEAD(__VA_ARGS__,) "
", \
 		                                                ^

ERROR:SPACING: space required after that ',' (ctx:VxB)
#295: FILE: drivers/net/hyperv/hyperv.c:54:
+			RTE_FMT_TAIL(__VA_ARGS__,)))
 			                        ^

ERROR:SPACING: space required after that ',' (ctx:VxB)
#302: FILE: drivers/net/hyperv/hyperv.c:61:
+			RTE_FMT_HEAD(__VA_ARGS__,) "
", \
 			                        ^

ERROR:SPACING: space required after that ',' (ctx:VxB)
#303: FILE: drivers/net/hyperv/hyperv.c:62:
+		RTE_FMT_TAIL(__VA_ARGS__,)))
 		                        ^

total: 4 errors, 4 warnings, 306 lines checked

           reply	other threads:[~2017-12-18 16:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20171218162443.12971-2-adrien.mazarguil@6wind.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=20171218164724.B331B3250@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=adrien.mazarguil@6wind.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).