From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bernard Iremonger <bernard.iremonger@intel.com>
Subject: [dpdk-test-report] |WARNING| pw63961 [PATCH v2 06/10] net/i40e: process ESP flows
Date: Tue, 17 Dec 2019 11:17:25 +0100 (CET) [thread overview]
Message-ID: <20191217101725.BC1EF1BF81@dpdk.org> (raw)
In-Reply-To: <1576577756-648-7-git-send-email-bernard.iremonger@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/63961
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <I40E_TUNNEL_TYPE_ESPoUDP>
#218: FILE: drivers/net/i40e/i40e_ethdev.h:788:
+ I40E_TUNNEL_TYPE_ESPoUDP,
CHECK:CAMELCASE: Avoid CamelCase: <I40E_TUNNEL_TYPE_ESPoIP>
#219: FILE: drivers/net/i40e/i40e_ethdev.h:789:
+ I40E_TUNNEL_TYPE_ESPoIP,
CHECK:CAMELCASE: Avoid CamelCase: <I40E_FDIR_IPv6_DEFAULT_VTC_FLOW>
#260: FILE: drivers/net/i40e/i40e_fdir.c:982:
+ ip6->vtc_flow = rte_cpu_to_be_32(I40E_FDIR_IPv6_DEFAULT_VTC_FLOW |
CHECK:CAMELCASE: Avoid CamelCase: <I40E_FDIR_IPv6_TC_OFFSET>
#261: FILE: drivers/net/i40e/i40e_fdir.c:983:
+ (fdir_input->flow.ipv6_flow.tc << I40E_FDIR_IPv6_TC_OFFSET));
CHECK:CAMELCASE: Avoid CamelCase: <I40E_FDIR_IPv6_PAYLOAD_LEN>
#262: FILE: drivers/net/i40e/i40e_fdir.c:984:
+ ip6->payload_len = rte_cpu_to_be_16(I40E_FDIR_IPv6_PAYLOAD_LEN);
CHECK:CAMELCASE: Avoid CamelCase: <I40E_FDIR_IPv6_DEFAULT_HOP_LIMITS>
#267: FILE: drivers/net/i40e/i40e_fdir.c:989:
+ I40E_FDIR_IPv6_DEFAULT_HOP_LIMITS;
total: 0 errors, 0 warnings, 6 checks, 524 lines checked
parent reply other threads:[~2019-12-17 10:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1576577756-648-7-git-send-email-bernard.iremonger@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=20191217101725.BC1EF1BF81@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=bernard.iremonger@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).