From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: [dpdk-test-report] |WARNING| pw48570 [v3, 5/9] ipsec: add SA data-path API
Date: Thu, 6 Dec 2018 18:43:05 +0100 (CET) [thread overview]
Message-ID: <20181206174305.6CB501B144@dpdk.org> (raw)
In-Reply-To: <1544110714-4514-6-git-send-email-konstantin.ananyev@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/48570
_coding style issues_
INFO: symbol is added but patch has insuficient context to determine the section name please ensure the version is EXPERIMENTAL
ERROR: symbol int32_t is added in a section other than 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
ERROR: symbol rc is added in a section other than the EXPERIMENTAL section of the version map
ERROR: symbol rc is added in a section other than the EXPERIMENTAL section of the version map
ERROR: symbol return is added in a section other than the EXPERIMENTAL section of the version map
ERROR: symbol return is added in a section other than 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
ERROR: symbol RTE_SET_USED(sa) is added in a section other than the EXPERIMENTAL section of the version map
ERROR: symbol ss->crypto.ses->opaque_data is added in a section other than the EXPERIMENTAL section of the version map
ERROR: symbol ss->pkt_func is added in a section other than the EXPERIMENTAL section of the version map
ERROR: symbol ss->security.ses->opaque_data is added in a section other than the EXPERIMENTAL section of the version map
ERROR: symbol struct is added in a section other than the EXPERIMENTAL section of the version map
parent reply other threads:[~2018-12-06 17:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1544110714-4514-6-git-send-email-konstantin.ananyev@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=20181206174305.6CB501B144@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=konstantin.ananyev@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).