From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: [dpdk-test-report] |WARNING| pw18258 [PATCH v4 01/25] ethdev: introduce generic flow API
Date: Tue, 20 Dec 2016 19:43:27 +0100 (CET) [thread overview]
Message-ID: <20161220184327.39592FBF2@dpdk.org> (raw)
In-Reply-To: <89884cb1e32f8e141b1e8a053cfdb334f9fff984.1482257521.git.adrien.mazarguil@6wind.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/18258
_coding style issues_
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#240: FILE: lib/librte_ether/rte_flow.c:58:
+ code = ENOSYS;
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#263: FILE: lib/librte_ether/rte_flow.c:81:
+ rte_flow_error_set(error, ENOSYS, RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#264: FILE: lib/librte_ether/rte_flow.c:82:
+ NULL, rte_strerror(ENOSYS));
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#283: FILE: lib/librte_ether/rte_flow.c:101:
+ rte_flow_error_set(error, ENOSYS, RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#284: FILE: lib/librte_ether/rte_flow.c:102:
+ NULL, rte_strerror(ENOSYS));
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#301: FILE: lib/librte_ether/rte_flow.c:119:
+ rte_flow_error_set(error, ENOSYS, RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#302: FILE: lib/librte_ether/rte_flow.c:120:
+ NULL, rte_strerror(ENOSYS));
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#318: FILE: lib/librte_ether/rte_flow.c:136:
+ rte_flow_error_set(error, ENOSYS, RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#319: FILE: lib/librte_ether/rte_flow.c:137:
+ NULL, rte_strerror(ENOSYS));
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#338: FILE: lib/librte_ether/rte_flow.c:156:
+ rte_flow_error_set(error, ENOSYS, RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#339: FILE: lib/librte_ether/rte_flow.c:157:
+ NULL, rte_strerror(ENOSYS));
total: 0 errors, 11 warnings, 1342 lines checked
parent reply other threads:[~2016-12-20 18:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <89884cb1e32f8e141b1e8a053cfdb334f9fff984.1482257521.git.adrien.mazarguil@6wind.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=20161220184327.39592FBF2@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=adrien.mazarguil@6wind.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).