From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
Subject: |WARNING| pw110353 [PATCH 01/17] net/bnxt: update HWRM structures
Date: Wed, 27 Apr 2022 17:00:52 +0200 (CEST) [thread overview]
Message-ID: <20220427150052.D1D7D1242B9@dpdk.org> (raw)
In-Reply-To: <20220427145821.5987-2-kalesh-anakkur.purayil@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/110353
_coding style issues_
WARNING:TYPO_SPELLING: 'hsi' may be misspelled - perhaps 'his'?
#57:
Brought in the latest hsi_struct_def_dpdk.h.
WARNING:TYPO_SPELLING: 'extrac' may be misspelled - perhaps 'extract'?
#905: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5719:
+ * {tuple_extrac_op[1:0],rss_profile_id[4:0],tuple_extrac_op[2]}.
WARNING:TYPO_SPELLING: 'extrac' may be misspelled - perhaps 'extract'?
#905: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5719:
+ * {tuple_extrac_op[1:0],rss_profile_id[4:0],tuple_extrac_op[2]}.
WARNING:TYPO_SPELLING: 'extrac' may be misspelled - perhaps 'extract'?
#906: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5720:
+ * The value of tuple_extrac_op provides the information about
WARNING:LONG_LINE: line length of 103 exceeds 100 columns
#1745: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:6559:
+ #define RX_PKT_COMPRESS_CMPL_ERRORS_AGG_BUFS_OPAQUE_ERRORS_PKT_ERROR_L4_BAD_HDR_LEN_TOO_SMALL \
WARNING:TYPO_SPELLING: 'extrac' may be misspelled - perhaps 'extract'?
#1995: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:7525:
+ * {tuple_extrac_op[1:0],rss_profile_id[4:0],tuple_extrac_op[2]}.
WARNING:TYPO_SPELLING: 'extrac' may be misspelled - perhaps 'extract'?
#1995: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:7525:
+ * {tuple_extrac_op[1:0],rss_profile_id[4:0],tuple_extrac_op[2]}.
WARNING:TYPO_SPELLING: 'extrac' may be misspelled - perhaps 'extract'?
#1997: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:7527:
+ * The value of tuple_extrac_op provides the information about
WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#2515: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:11571:
+ #define HWRM_ASYNC_EVENT_CMPL_PHC_UPDATE_EVENT_DATA2_PHC_MASTER_FID_MASK \
WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#2518: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:11573:
+ #define HWRM_ASYNC_EVENT_CMPL_PHC_UPDATE_EVENT_DATA2_PHC_MASTER_FID_SFT \
WARNING:TYPO_SPELLING: 'MASTER' may be misspelled - perhaps 'PRIMARY'?
#2558: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:11605:
+ #define HWRM_ASYNC_EVENT_CMPL_PHC_UPDATE_EVENT_DATA1_FLAGS_PHC_MASTER \
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#3137: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:21756:
+ /* TIM. */
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#3138: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:21757:
+ #define HWRM_FUNC_BACKING_STORE_QCFG_V2_INPUT_TYPE_TIM \
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#3217: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:21836:
+ /* TIM. */
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#3218: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:21837:
+ #define HWRM_FUNC_BACKING_STORE_QCFG_V2_OUTPUT_TYPE_TIM \
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#3402: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:22021:
+ /* TIM. */
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#3403: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:22022:
+ #define HWRM_FUNC_BACKING_STORE_QCAPS_V2_INPUT_TYPE_TIM \
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#3476: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:22095:
+ /* TIM. */
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#3477: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:22096:
+ #define HWRM_FUNC_BACKING_STORE_QCAPS_V2_OUTPUT_TYPE_TIM \
total: 0 errors, 19 warnings, 0 checks, 4741 lines checked
parent reply other threads:[~2022-04-27 15:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220427145821.5987-2-kalesh-anakkur.purayil@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=20220427150052.D1D7D1242B9@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=kalesh-anakkur.purayil@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).