From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
Subject: [dpdk-test-report] |WARNING| pw52802 [PATCH v5 1/2] timer: allow timer management in shared memory
Date: Mon, 15 Apr 2019 23:44:06 +0200 (CEST) [thread overview]
Message-ID: <20190415214406.597601B433@dpdk.org> (raw)
In-Reply-To: <1555364488-28207-2-git-send-email-erik.g.carrillo@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/52802
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#46:
[1] https://doc.dpdk.org/guides/prog_guide/multi_proc_support.html#multi-process-limitations
WARNING:MACRO_WITH_FLOW_CONTROL: Macros with flow control statements should be avoided
#139: FILE: lib/librte_timer/rte_timer.c:88:
+#define TIMER_DATA_VALID_GET_OR_ERR_RET(id, timer_data, retval) do { \
+ if (id >= RTE_MAX_DATA_ELS || !timer_data_valid(id)) \
+ return retval; \
+ timer_data = &rte_timer_data_arr[id]; \
+} while (0)
total: 0 errors, 2 warnings, 1030 lines checked
ERROR: symbol rte_timer_dump_stats is added in the DPDK_19.05 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_timer_manage is added in the DPDK_19.05 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_timer_reset is added in the DPDK_19.05 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_timer_stop is added in the DPDK_19.05 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_timer_subsystem_init 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-04-15 21:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1555364488-28207-2-git-send-email-erik.g.carrillo@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=20190415214406.597601B433@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=erik.g.carrillo@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).