From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <jerinj@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw66900 [PATCH v1 06/26] graph: populate fastpath memory for graph reel
Date: Wed, 18 Mar 2020 22:37:38 +0100 (CET) [thread overview]
Message-ID: <20200318213738.B73FB1C199@dpdk.org> (raw)
In-Reply-To: <20200318213551.3489504-7-jerinj@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/66900
_coding style issues_
INFO: symbol __rte_node_stream_alloc has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_node_stream_alloc(struct is added but patch has insuficient context to determine the section name please ensure the version is EXPERIMENTAL
ERROR: symbol char is added in the rte_graph section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol char is added in the rte_node section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol int is added in the rte_graph section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_edge_t is added in the rte_node section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_graph_off_t is added in the rte_graph section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_graph_off_t is added in the rte_node section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_graph_t is added in the rte_graph section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_node_process_t is added in the union section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_node_t is added in the rte_graph section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_node_t is added in the rte_node section, but is expected to be added in the EXPERIMENTAL section of the version map
INFO: symbol struct is added but patch has insuficient context to determine the section name please ensure the version is EXPERIMENTAL
ERROR: symbol uint16_t is added in the rte_node section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol uint32_t is added in the rte_graph section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol uint32_t is added in the rte_node section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol uint64_t is added in the rte_graph section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol uint64_t is added in the rte_node section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol uint64_t is added in the union section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol uint8_t is added in the rte_node section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol void is added in the union section, but is expected to be added in the EXPERIMENTAL section of the version map
INFO: symbol } is added but patch has insuficient context to determine the section name please ensure the version is EXPERIMENTAL
parent reply other threads:[~2020-03-18 21:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200318213551.3489504-7-jerinj@marvell.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=20200318213738.B73FB1C199@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jerinj@marvell.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).