From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: [dpdk-test-report] |WARNING| pw56690 [PATCH 22/22] net/bnxt: update HWRM API to version 1.10.0.91
Date: Thu, 18 Jul 2019 05:39:25 +0200 (CEST) [thread overview]
Message-ID: <20190718033925.4BD751B9AA@dpdk.org> (raw)
In-Reply-To: <20190718033616.37605-23-ajit.khaparde@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/56690
_coding style issues_
WARNING:TYPO_SPELLING: 'preceed' may be misspelled - perhaps 'precede'?
#947: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:3982:
+ * preceed the TPA End completion. If the value is zero, then the
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#1124: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:4603:
+ /* Indicates the physical function this event occured on. */
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#1133: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5584:
+ /* Indicates the physical function this event occured on. */
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#1142: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5932:
+ /* Indicates the physical function this event occured on. */
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#1148: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5937:
+ /* Indicates the virtual function this event occured on */
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#1157: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5987:
+ /* Indicates flow ID this event occured on. */
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#1163: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5992:
+ /* Indicates flow direction this event occured on. */
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#1172: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:6108:
+ /* Indicates function ID that this event occured on. */
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#1181: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:6190:
+ /* Indicates the 2nd global id this event occured on. */
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#1190: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:6226:
+ /* Indicates the 1st global id this event occured on. */
WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#1199: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:6246:
+ * Indicates EEM flow aging mode this event occured on. If
WARNING:LONG_LINE_COMMENT: line over 90 characters
#1471: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:28965:
+ * Set to 1 to indicate flow flush operation to cleanup all the flows by the caller.
WARNING:LONG_LINE_COMMENT: line over 90 characters
#1472: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:28966:
+ * This flag is set to 0 by older driver. For older firmware, setting this flag has no effect.
WARNING:TYPO_SPELLING: 'auxillary' may be misspelled - perhaps 'auxiliary'?
#1672: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:31204:
+ * that are input as auxillary data.
WARNING:TYPO_SPELLING: 'auxillary' may be misspelled - perhaps 'auxiliary'?
#1679: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:31210:
+ * that are output as auxillary data.
WARNING:TYPO_SPELLING: 'auxillary' may be misspelled - perhaps 'auxiliary'?
#1715: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:31562:
+ * that are input as auxillary data.
WARNING:TYPO_SPELLING: 'auxillary' may be misspelled - perhaps 'auxiliary'?
#1722: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:31568:
+ * that are output as auxillary data.
total: 0 errors, 17 warnings, 0 checks, 1664 lines checked
parent reply other threads:[~2019-07-18 3:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20190718033616.37605-23-ajit.khaparde@broadcom.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=20190718033925.4BD751B9AA@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ajit.khaparde@broadcom.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).