From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Nikos Dragazis <ndragazis@arrikto.com>
Subject: [dpdk-test-report] |WARNING| pw54971 [PATCH 17/28] vhost: support registering additional vhost-user transports
Date: Wed, 19 Jun 2019 17:18:09 +0200 (CEST) [thread overview]
Message-ID: <20190619151809.6A3991C416@dpdk.org> (raw)
In-Reply-To: <1560957293-17294-18-git-send-email-ndragazis@arrikto.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/54971
_coding style issues_
WARNING:LONG_LINE: line over 90 characters
#91: FILE: lib/librte_vhost/socket.c:326:
+ if (rte_vhost_register_transport(VHOST_TRANSPORT_UNIX, &af_unix_trans_ops) < 0)
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#142: FILE: lib/librte_vhost/vhost.h:513:
+ * */
ERROR:CODE_INDENT: code indent should use tabs where possible
#145: FILE: lib/librte_vhost/vhost.h:516:
+ const struct vhost_transport_ops *trans_ops);$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#145: FILE: lib/librte_vhost/vhost.h:516:
+ const struct vhost_transport_ops *trans_ops);$
total: 1 errors, 3 warnings, 88 lines checked
ERROR: symbol rte_vhost_register_transport is added in the DPDK_19.05 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol vhost_destroy_device is added in the DPDK_19.05 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol vhost_new_device is added in the DPDK_19.05 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol vhost_set_ifname is added in the DPDK_19.05 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol vhost_user_msg_handler is added in the DPDK_19.05 section, but is expected to be added in the EXPERIMENTAL section of the version map
parent reply other threads:[~2019-06-19 15:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1560957293-17294-18-git-send-email-ndragazis@arrikto.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=20190619151809.6A3991C416@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ndragazis@arrikto.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).