automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <jerinj@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw67351 [PATCH v3 32/33] mempool: add tracepoints
Date: Sun, 29 Mar 2020 16:51:38 +0200 (CEST)	[thread overview]
Message-ID: <20200329145138.AD0EF1C1FB@dpdk.org> (raw)
In-Reply-To: <20200329144342.1543749-33-jerinj@marvell.com>

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

_coding style issues_


INFO: symbol __rte_trace_lib_mempool_cache_create has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_cache_flush has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_cache_free has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_create has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_create_empty has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_default_cache has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_free has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_generic_get has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_generic_put has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_get_bulk has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_get_contig_blocks has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_get_page_size has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_ops_alloc has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_ops_dequeue_bulk has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_ops_dequeue_contig_blocks has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_ops_enqueue_bulk has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_ops_free has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_ops_populate has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_populate_anon has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_populate_default has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_populate_iova has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_populate_virt has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_put_bulk has been added to the EXPERIMENTAL section of the version map
INFO: symbol __rte_trace_lib_mempool_set_ops_byname has been added to the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_long(len) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_long(pg_sz) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_ptr(addr) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_ptr(cache) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_ptr(default_cache) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_ptr(mempool) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_ptr(mp_init_arg) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_ptr(obj_cb) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_ptr(obj_init_arg) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_ptr(opaque) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_ptr(vaddr) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_string(name) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_u32(cache->flushthresh) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_u32(elt_size) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_u32(max_objs) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_u32(nb_objs) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_u32(private_data_size) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_u32(size) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_trace_ctf_u64(iova) is added in the "C" section, but is expected to be added in the EXPERIMENTAL section of the version map

           reply	other threads:[~2020-03-29 14:51 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20200329144342.1543749-33-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=20200329145138.AD0EF1C1FB@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).