From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andrey Vesnovaty <andrey.vesnovaty@gmail.com>
Subject: [dpdk-test-report] |WARNING| pw71820 [RFC v2 1/1] add flow shared action API
Date: Sat, 20 Jun 2020 15:34:36 +0200 (CEST) [thread overview]
Message-ID: <20200620133436.924101BFA3@dpdk.org> (raw)
In-Reply-To: <20200620133257.12441-1-andrey.vesnovaty@gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/71820
_coding style issues_
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#266: FILE: lib/librte_ethdev/rte_flow.c:1252:
+ rte_flow_error_set(error, ENOSYS, RTE_FLOW_ERROR_TYPE_UNSPECIFIED,
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#267: FILE: lib/librte_ethdev/rte_flow.c:1253:
+ NULL, rte_strerror(ENOSYS));
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#285: FILE: lib/librte_ethdev/rte_flow.c:1271:
+ return rte_flow_error_set(error, ENOSYS,
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#287: FILE: lib/librte_ethdev/rte_flow.c:1273:
+ NULL, rte_strerror(ENOSYS));
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#305: FILE: lib/librte_ethdev/rte_flow.c:1291:
+ return rte_flow_error_set(error, ENOSYS,
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#307: FILE: lib/librte_ethdev/rte_flow.c:1293:
+ NULL, rte_strerror(ENOSYS));
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#325: FILE: lib/librte_ethdev/rte_flow.c:1311:
+ return rte_flow_error_set(error, ENOSYS,
WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#327: FILE: lib/librte_ethdev/rte_flow.c:1313:
+ NULL, rte_strerror(ENOSYS));
WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Andrey Vesnovaty <andrey.vesnovaty@gmail.com>'
total: 0 errors, 9 warnings, 289 lines checked
parent reply other threads:[~2020-06-20 13:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200620133257.12441-1-andrey.vesnovaty@gmail.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=20200620133436.924101BFA3@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=andrey.vesnovaty@gmail.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).