[dpdk-test-report] |WARNING| pw79231 [PATCH 2/3] net/bnxt: update HWRM structures

automatic DPDK test reports
 help / color / mirror / Atom feed

From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: [dpdk-test-report] |WARNING| pw79231 [PATCH 2/3] net/bnxt: update HWRM structures
Date: Tue, 29 Sep 2020 23:01:52 +0200 (CEST)	[thread overview]
Message-ID: <20200929210152.BC06F1D54B@dpdk.org> (raw)
In-Reply-To: <20200929205935.20432-3-ajit.khaparde@broadcom.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/79231

_coding style issues_


WARNING:TYPO_SPELLING: 'statitics' may be misspelled - perhaps 'statistics'?
#269: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:626:
+	/* Queries extended statitics context */

WARNING:TYPO_SPELLING: 'thru' may be misspelled - perhaps 'through'?
#371: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:1575:
+	uint8_t	write_thru_table_type;

WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#385: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:1589:
+	#define CFA_BDS_WRITE_CMD_DATA_MSG_WRITE_THRU       UINT32_C(0x10)

WARNING:TYPO_SPELLING: 'thru' may be misspelled - perhaps 'through'?
#477: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:1681:
+	uint8_t	write_thru;

WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#484: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:1688:
+	#define CFA_BDS_EM_INSERT_CMD_DATA_MSG_WRITE_THRU     UINT32_C(0x10)

WARNING:TYPO_SPELLING: 'thru' may be misspelled - perhaps 'through'?
#525: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:1729:
+	uint8_t	write_thru;

WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#532: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:1736:
+	#define CFA_BDS_EM_DELETE_CMD_DATA_MSG_WRITE_THRU     UINT32_C(0x10)

WARNING:TYPO_SPELLING: 'Berkley' may be misspelled - perhaps ''?
#884: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:2088:
+	 * between the TCP stack and Device Driver (Berkley Packet Filter for

WARNING:TYPO_SPELLING: 'fiels' may be misspelled - perhaps 'feels'?
#1821: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:9690:
+	/* Meta data fiels are not valid */

WARNING:TYPO_SPELLING: 'atleast' may be misspelled - perhaps 'at least'?
#1933: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:9802:
+	 * This enumeration states that there is atleast one tag in the

WARNING:TYPO_SPELLING: 'atleast' may be misspelled - perhaps 'at least'?
#1934: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:9803:
+	 * packet and atleast one of the tag is invalid. The entire packet

WARNING:TYPO_SPELLING: 'atleast' may be misspelled - perhaps 'at least'?
#2044: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:9913:
+	 * This enumeration states that there is atleast one tag in the

WARNING:TYPO_SPELLING: 'atleast' may be misspelled - perhaps 'at least'?
#2045: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:9914:
+	 * packet and atleast one of the tag is invalid. The entire packet

WARNING:TYPO_SPELLING: 'advertisment' may be misspelled - perhaps 'advertisement'?
#2540: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:17281:
+	 * The default advertisment setting can be queried by calling

WARNING:TYPO_SPELLING: 'exsiting' may be misspelled - perhaps 'existing'?
#3789: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:37898:
+	/* Modify exsiting rep2fn pairs paired with same PF and move pairs to new PF. */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#4945: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:38833:
+	/* Minimum guaranteed number of flow counters supported for this function, in RX direction. */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#4947: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:38835:
+	/* Maximum non-guaranteed number of flow counters supported for this function, in RX direction. */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#4949: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:38837:
+	/* Minimum guaranteed number of flow counters supported for this function, in TX direction. */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#4951: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:38839:
+	/* Maximum non-guaranteed number of flow counters supported for this function, in TX direction. */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#4953: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:38841:
+	/* Minimum guaranteed number of extension flow counters supported for this function, in RX direction. */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#4955: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:38843:
+	/* Maximum non-guaranteed number of extension flow counters supported for this function, in RX direction. */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#4957: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:38845:
+	/* Minimum guaranteed number of extension flow counters supported for this function, in TX direction. */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#4959: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:38847:
+	/* Maximum non-guaranteed number of extension flow counters supported for this function, in TX direction. */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#4961: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:38849:
+	/* Minimum guaranteed number of meter drop counters supported for this function, in RX direction. */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#4963: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:38851:
+	/* Maximum non-guaranteed number of meter drop counters supported for this function, in RX direction. */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#4965: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:38853:
+	/* Minimum guaranteed number of meter drop counters supported for this function, in TX direction. */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#4967: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:38855:
+	/* Maximum non-guaranteed number of meter drop counters supported for this function, in TX direction. */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#12083: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:44709:
+	/* The Directory Entry Type (valid values are defined in the bnxnvm_directory_type enum defined in the file bnxnvm_defs.h). */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#12101: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:44721:
+	 * Length of data to write, in bytes. May be less than or equal to the allocated size for the directory entry.

WARNING:LONG_LINE_COMMENT: line over 100 characters
#12102: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:44722:
+	 * The data length stored in the directory entry will be updated to reflect this value once the write is complete.

WARNING:LONG_LINE_COMMENT: line over 100 characters
#12115: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:44735:
+	 * The requested length of the allocated NVM for the item, in bytes. This value may be greater than or equal to the specified data length (dir_data_length).

WARNING:LONG_LINE_COMMENT: line over 100 characters
#12117: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:44737:
+	 * The response will contain the actual allocated item length, which may be greater than the requested item length.

WARNING:LONG_LINE_COMMENT: line over 100 characters
#12118: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:44738:
+	 * The purpose for allocating more than the required number of bytes for an item's data is to pre-allocate extra storage (padding) to accommodate

WARNING:LONG_LINE_COMMENT: line over 100 characters
#12119: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:44739:
+	 * the potential future growth of an item (e.g. upgraded firmware with a size increase, log growth, expanded configuration data).

WARNING:LONG_LINE_COMMENT: line over 100 characters
#12138: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:44756:
+	 * Length of the allocated NVM for the item, in bytes. The value may be greater than or equal to the specified data length or the requested item length.

WARNING:LONG_LINE_COMMENT: line over 100 characters
#12139: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:44757:
+	 * The actual item length used when creating a new directory entry will be a multiple of an NVM block size.

WARNING:LONG_LINE_COMMENT: line over 100 characters
#12567: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:45101:
+	/* Available size that can be used, in bytes.  Available size is the NVRAM size take away the used size and reserved size. */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#12754: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:45243:
+	/* The Directory Entry Extension flags (see BNX_DIR_EXT_* for extension flag definitions). */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#12971: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:45412:
+	 * If set to 1, then unspecified images, images not in the package file, will be safely deleted.

WARNING:LONG_LINE_COMMENT: line over 100 characters
#13356: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:45798:
+	/* When this bit is 1, flush internal cache after this write operation (see hwrm_nvm_flush command.) */

WARNING:LONG_LINE_COMMENT: line over 100 characters
#13658: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:46100:
+	/* AP processor complex (in multi-host environment). Use host_idx to control which core is reset */

total: 0 errors, 41 warnings, 0 checks, 13500 lines checked

          parent reply	other threads:[~2020-09-29 21:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20200929205935.20432-3-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=20200929210152.BC06F1D54B@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).