From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: |WARNING| pw129738 [PATCH v6 2/3] log: separate logging functions out of EAL
Date: Mon, 31 Jul 2023 12:18:35 +0200 (CEST) [thread overview]
Message-ID: <20230731101835.47A7A12069D@dpdk.org> (raw)
In-Reply-To: <20230731101703.1178204-3-bruce.richardson@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/129738
_coding style issues_
INFO: symbol rte_log_can_log is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_log_cur_msg_loglevel is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_log_cur_msg_logtype is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_log is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_log_dump is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_log_get_global_level is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_log_get_level is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_log_get_stream is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_log_list_types is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_log_register is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_log_register_type_and_pick_level is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_log_set_global_level is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_log_set_level is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_log_set_level_pattern is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_log_set_level_regexp is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_openlog_stream is being removed, ensure that it has gone through the deprecation process
INFO: symbol rte_vlog is being removed, ensure that it has gone through the deprecation process
INFO: symbol eal_log_init has been added to the INTERNAL section of the version map
INFO: symbol eal_log_level2str has been added to the INTERNAL section of the version map
INFO: symbol eal_log_save_pattern has been added to the INTERNAL section of the version map
INFO: symbol eal_log_save_regexp has been added to the INTERNAL section of the version map
INFO: symbol eal_log_set_default has been added to the INTERNAL section of the version map
INFO: symbol rte_eal_log_cleanup has been added to the INTERNAL section of the version map
ERROR: symbol rte_log_can_log is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_log_cur_msg_loglevel is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_log_cur_msg_logtype is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_log is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_log_dump is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_log_get_global_level is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_log_get_level is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_log_get_stream is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_log_list_types is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_log_register is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_log_register_type_and_pick_level is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_log_set_global_level is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_log_set_level is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_log_set_level_pattern is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_log_set_level_regexp is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_openlog_stream is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_vlog is added in the DPDK_24 section, but is expected to be added in the EXPERIMENTAL section of the version map
parent reply other threads:[~2023-07-31 10:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230731101703.1178204-3-bruce.richardson@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=20230731101835.47A7A12069D@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=bruce.richardson@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).