From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: [dpdk-test-report] |WARNING| pw32008 [PATCH 12/14] net/dpaa2: optimize Rx path packet parsing
Date: Fri, 8 Dec 2017 06:24:14 +0100 (CET) [thread overview]
Message-ID: <20171208052414.0DA2D199B4@dpdk.org> (raw)
In-Reply-To: <1512710487-32388-13-git-send-email-hemant.agrawal@nxp.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/32008
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <DPAA2_L3_IPv4>
#35: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpni_annot.h:222:
+#define DPAA2_L3_IPv4 (L3_IPV4_1_PRESENT | L3_IPV4_1_UNICAST | \
CHECK:CAMELCASE: Avoid CamelCase: <DPAA2_L3_IPv6>
#38: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpni_annot.h:225:
+#define DPAA2_L3_IPv6 (L3_IPV6_1_PRESENT | L3_IPV6_1_UNICAST | \
CHECK:CAMELCASE: Avoid CamelCase: <DPAA2_L3_IPv4_TCP>
#41: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpni_annot.h:228:
+#define DPAA2_L3_IPv4_TCP (L3_IPV4_1_PRESENT | L3_IPV4_1_UNICAST | \
CHECK:CAMELCASE: Avoid CamelCase: <DPAA2_L3_IPv4_UDP>
#45: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpni_annot.h:232:
+#define DPAA2_L3_IPv4_UDP (L3_IPV4_1_PRESENT | L3_IPV4_1_UNICAST | \
CHECK:CAMELCASE: Avoid CamelCase: <DPAA2_L3_IPv6_TCP>
#48: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpni_annot.h:235:
+#define DPAA2_L3_IPv6_TCP (L3_IPV6_1_PRESENT | L3_IPV6_1_UNICAST | \
CHECK:CAMELCASE: Avoid CamelCase: <DPAA2_L3_IPv6_UDP>
#52: FILE: drivers/net/dpaa2/base/dpaa2_hw_dpni_annot.h:239:
+#define DPAA2_L3_IPv6_UDP (L3_IPV6_1_PRESENT | L3_IPV6_1_UNICAST | \
total: 0 errors, 0 warnings, 6 checks, 99 lines checked
parent reply other threads:[~2017-12-08 5:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1512710487-32388-13-git-send-email-hemant.agrawal@nxp.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=20171208052414.0DA2D199B4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=hemant.agrawal@nxp.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).