From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: [dpdk-test-report] |WARNING| pw38044 [PATCH v4 02/10] bpf: add BPF loading and execution framework
Date: Fri, 13 Apr 2018 16:44:48 +0200 (CEST) [thread overview]
Message-ID: <20180413144448.1C7E11C650@dpdk.org> (raw)
In-Reply-To: <1523630598-24606-3-git-send-email-konstantin.ananyev@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/38044
_coding style issues_
WARNING:SPACING: space prohibited between function name and open parenthesis '('
#212: FILE: lib/librte_bpf/bpf_exec.c:25:
+ ((type)(reg)[(ins)->dst_reg] op (type)(reg)[(ins)->src_reg]) ? \
WARNING:SPACING: space prohibited between function name and open parenthesis '('
#217: FILE: lib/librte_bpf/bpf_exec.c:30:
+ ((type)(reg)[(ins)->dst_reg] op (type)(ins)->imm) ? \
WARNING:SPACING: space prohibited between function name and open parenthesis '('
#228: FILE: lib/librte_bpf/bpf_exec.c:41:
+ (type)(reg)[(ins)->dst_reg] op (type)(reg)[(ins)->src_reg])
WARNING:SPACING: space prohibited between function name and open parenthesis '('
#235: FILE: lib/librte_bpf/bpf_exec.c:48:
+ (type)(reg)[(ins)->dst_reg] op (type)(ins)->imm)
WARNING:MACRO_WITH_FLOW_CONTROL: Macros with flow control statements should be avoided
#237: FILE: lib/librte_bpf/bpf_exec.c:50:
+#define BPF_DIV_ZERO_CHECK(bpf, reg, ins, type) do { \
+ if ((type)(reg)[(ins)->src_reg] == 0) { \
+ RTE_BPF_LOG(ERR, \
+ "%s(%p): division by 0 at pc: %#zx;
", \
+ __func__, bpf, \
+ (uintptr_t)(ins) - (uintptr_t)(bpf)->prm.ins); \
+ return 0; \
+ } \
+} while (0)
total: 0 errors, 5 warnings, 1255 lines checked
parent reply other threads:[~2018-04-13 14:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1523630598-24606-3-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=20180413144448.1C7E11C650@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).