From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andy Pei <andy.pei@intel.com>
Subject: [dpdk-test-report] |WARNING| pw54949 [PATCH v3 4/4] net/ipn3ke: implementation of statistics
Date: Wed, 19 Jun 2019 16:32:29 +0200 (CEST) [thread overview]
Message-ID: <20190619143229.E5A6D1C2FF@dpdk.org> (raw)
In-Reply-To: <1560934174-408632-4-git-send-email-andy.pei@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/54949
_coding style issues_
CHECK:CAMELCASE: Avoid CamelCase: <ipn3ke_rpst_25G_NICside_TX_stats_reset>
#276: FILE: drivers/net/ipn3ke/ipn3ke_representor.c:533:
+ipn3ke_rpst_25G_NICside_TX_stats_reset(struct ipn3ke_hw *hw,
CHECK:CAMELCASE: Avoid CamelCase: <ipn3ke_rpst_25G_NICside_RX_stats_reset>
#305: FILE: drivers/net/ipn3ke/ipn3ke_representor.c:562:
+ipn3ke_rpst_25G_NICside_RX_stats_reset(struct ipn3ke_hw *hw,
CHECK:CAMELCASE: Avoid CamelCase: <ipn3ke_rpst_10G_NICside_TX_stats_reset>
#334: FILE: drivers/net/ipn3ke/ipn3ke_representor.c:591:
+ipn3ke_rpst_10G_NICside_TX_stats_reset(struct ipn3ke_hw *hw,
CHECK:CAMELCASE: Avoid CamelCase: <ipn3ke_rpst_10G_NICside_RX_stats_reset>
#359: FILE: drivers/net/ipn3ke/ipn3ke_representor.c:616:
+ipn3ke_rpst_10G_NICside_RX_stats_reset(struct ipn3ke_hw *hw,
CHECK:CAMELCASE: Avoid CamelCase: <ipn3ke_read_25G_Lineside_stats_registers>
#386: FILE: drivers/net/ipn3ke/ipn3ke_representor.c:641:
+ipn3ke_read_25G_Lineside_stats_registers
CHECK:CAMELCASE: Avoid CamelCase: <ipn3ke_rpst_25G_Lineside_TX_stats_reset>
#1756: FILE: drivers/net/ipn3ke/ipn3ke_representor.c:2011:
+ipn3ke_rpst_25G_Lineside_TX_stats_reset(struct ipn3ke_hw *hw,
CHECK:CAMELCASE: Avoid CamelCase: <ipn3ke_rpst_25G_Lineside_RX_stats_reset>
#1785: FILE: drivers/net/ipn3ke/ipn3ke_representor.c:2040:
+ipn3ke_rpst_25G_Lineside_RX_stats_reset(struct ipn3ke_hw *hw,
CHECK:CAMELCASE: Avoid CamelCase: <ipn3ke_read_10G_Lineside_stats_registers>
#1816: FILE: drivers/net/ipn3ke/ipn3ke_representor.c:2069:
+ipn3ke_read_10G_Lineside_stats_registers
CHECK:CAMELCASE: Avoid CamelCase: <ipn3ke_rpst_10G_Lineside_TX_stats_reset>
#3118: FILE: drivers/net/ipn3ke/ipn3ke_representor.c:3371:
+ipn3ke_rpst_10G_Lineside_TX_stats_reset(struct ipn3ke_hw *hw,
CHECK:CAMELCASE: Avoid CamelCase: <ipn3ke_rpst_10G_Lineside_RX_stats_reset>
#3143: FILE: drivers/net/ipn3ke/ipn3ke_representor.c:3396:
+ipn3ke_rpst_10G_Lineside_RX_stats_reset(struct ipn3ke_hw *hw,
total: 0 errors, 0 warnings, 10 checks, 3468 lines checked
parent reply other threads:[~2019-06-19 14:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1560934174-408632-4-git-send-email-andy.pei@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=20190619143229.E5A6D1C2FF@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=andy.pei@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).