From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Subject: [dpdk-test-report] |WARNING| pw49355 [2/4] net/mlx5: add tos and ttl fields support on E-Switch
Date: Sat, 29 Dec 2018 19:52:30 +0100 (CET) [thread overview]
Message-ID: <20181229185230.3B9115F2A@dpdk.org> (raw)
In-Reply-To: <1546109501-24865-3-git-send-email-viacheslavo@mellanox.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/49355
_coding style issues_
CHECK:SPACING: No space is necessary after a cast
#114: FILE: drivers/net/mlx5/mlx5_flow_tcf.c:2519:
+ size += SZ_NLATTR_TYPE_OF(uint8_t) * 2;
CHECK:SPACING: No space is necessary after a cast
#116: FILE: drivers/net/mlx5/mlx5_flow_tcf.c:2521:
+ size += SZ_NLATTR_TYPE_OF(uint8_t) * 2;
CHECK:SPACING: No space is necessary after a cast
#127: FILE: drivers/net/mlx5/mlx5_flow_tcf.c:2531:
+ size += SZ_NLATTR_TYPE_OF(uint8_t) * 2;
CHECK:SPACING: No space is necessary after a cast
#130: FILE: drivers/net/mlx5/mlx5_flow_tcf.c:2534:
+ size += SZ_NLATTR_TYPE_OF(uint8_t) * 2;
CHECK:SPACING: No space is necessary after a cast
#146: FILE: drivers/net/mlx5/mlx5_flow_tcf.c:2609:
+ size += SZ_NLATTR_TYPE_OF(uint8_t) * 2;
CHECK:SPACING: No space is necessary after a cast
#148: FILE: drivers/net/mlx5/mlx5_flow_tcf.c:2611:
+ size += SZ_NLATTR_TYPE_OF(uint8_t) * 2;
CHECK:SPACING: No space is necessary after a cast
#157: FILE: drivers/net/mlx5/mlx5_flow_tcf.c:2619:
+ size += SZ_NLATTR_TYPE_OF(uint8_t) * 2;
CHECK:SPACING: No space is necessary after a cast
#160: FILE: drivers/net/mlx5/mlx5_flow_tcf.c:2622:
+ size += SZ_NLATTR_TYPE_OF(uint8_t) * 2;
total: 0 errors, 0 warnings, 8 checks, 285 lines checked
parent reply other threads:[~2018-12-29 18:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1546109501-24865-3-git-send-email-viacheslavo@mellanox.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=20181229185230.3B9115F2A@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=test-report@dpdk.org \
--cc=viacheslavo@mellanox.com \
/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).