From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: JinYu <jin.yu@intel.com>
Subject: [dpdk-test-report] |WARNING| pw56223 [PATCH v2] [v2, 1/2]vhost: support inflight share memory protocol feature
Date: Mon, 8 Jul 2019 12:15:11 +0200 (CEST) [thread overview]
Message-ID: <20190708101511.3971A1B952@dpdk.org> (raw)
In-Reply-To: <20190708180005.47196-2-jin.yu@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/56223
_coding style issues_
WARNING:LONG_LINE: line over 90 characters
#271: FILE: lib/librte_vhost/vhost.c:778:
+ vring->resubmit_inflight_split = dev->virtqueue[vring_idx]->resubmit_inflight_split;
WARNING:UNNECESSARY_ELSE: else is not generally useful after a break or return
#593: FILE: lib/librte_vhost/vhost_user.c:1282:
+ return RTE_VHOST_MSG_RESULT_ERR;
+ } else {
WARNING:UNNECESSARY_ELSE: else is not generally useful after a break or return
#652: FILE: lib/librte_vhost/vhost_user.c:1341:
+ return RTE_VHOST_MSG_RESULT_ERR;
+ } else {
WARNING:LONG_LINE: line over 90 characters
#745: FILE: lib/librte_vhost/vhost_user.c:1463:
+ vq->inflight_split->desc[vq->inflight_split->last_inflight_io].inflight = 0;
total: 0 errors, 4 warnings, 764 lines checked
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
Please only put __rte_experimental tags in headers (b/lib/librte_vhost/vhost.c)
__rte_experimental must appear alone on the line immediately preceding the return type of a function.
parent reply other threads:[~2019-07-08 10:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190708180005.47196-2-jin.yu@intel.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=20190708101511.3971A1B952@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jin.yu@intel.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).