From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: [dpdk-test-report] |WARNING| pw53837 [PATCH 09/25] eal: add EAL tailq list lock/unlock API
Date: Wed, 29 May 2019 18:33:05 +0200 (CEST) [thread overview]
Message-ID: <20190529163305.BCB7B1B99B@dpdk.org> (raw)
In-Reply-To: <e14dbb4c4232fdf843456de5de97bf1a15783a83.1559147228.git.anatoly.burakov@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/53837
_coding style issues_
ERROR: symbol rte_eal_mcfg_tailq_read_lock is added in the DPDK_19.08 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_eal_mcfg_tailq_read_unlock is added in the DPDK_19.08 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_eal_mcfg_tailq_write_lock is added in the DPDK_19.08 section, but is expected to be added in the EXPERIMENTAL section of the version map
ERROR: symbol rte_eal_mcfg_tailq_write_unlock is added in the DPDK_19.08 section, but is expected to be added in the EXPERIMENTAL section of the version map
parent reply other threads:[~2019-05-29 16:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <e14dbb4c4232fdf843456de5de97bf1a15783a83.1559147228.git.anatoly.burakov@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=20190529163305.BCB7B1B99B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=anatoly.burakov@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).