From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
Subject: [dpdk-test-report] |WARNING| pw27372 [PATCH v1 06/21] net/mlx5: verify all flows are been removed on close
Date: Wed, 2 Aug 2017 16:11:55 +0200 (CEST) [thread overview]
Message-ID: <20170802141155.F2BDCA2C3@dpdk.org> (raw)
In-Reply-To: <e9e86de4a00890a20ca993a59aaade8c01505501.1501681927.git.nelio.laranjeiro@6wind.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/27372
_coding style issues_
ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#34: FILE: drivers/net/mlx5/mlx5.c:205:
+ WARN("%p: some flows still remain", (void*)priv);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct priv *' should also have an identifier name
#46: FILE: drivers/net/mlx5/mlx5.h:290:
+int priv_flow_verify(struct priv *);
ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#73: FILE: drivers/net/mlx5/mlx5_flow.c:1658:
+ DEBUG("%p: flow %p still referenced", (void*)priv,
ERROR:POINTER_LOCATION: "(foo*)" should be "(foo *)"
#74: FILE: drivers/net/mlx5/mlx5_flow.c:1659:
+ (void*)flow);
total: 3 errors, 1 warnings, 0 checks, 40 lines checked
parent reply other threads:[~2017-08-02 14:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <e9e86de4a00890a20ca993a59aaade8c01505501.1501681927.git.nelio.laranjeiro@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=20170802141155.F2BDCA2C3@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=nelio.laranjeiro@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).