automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Lance Richardson <lance.richardson@broadcom.com>
Subject: [dpdk-test-report] |WARNING| pw53820 [PATCH v4 7/8] net/bnxt: update HWRM API to version 1.10.0.48
Date: Wed, 29 May 2019 17:04:20 +0200 (CEST)	[thread overview]
Message-ID: <20190529150420.A50061B953@dpdk.org> (raw)
In-Reply-To: <20190529150234.15166-8-lance.richardson@broadcom.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4460 bytes --]

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

_coding style issues_


WARNING:LONG_LINE_COMMENT: line over 90 characters
#182: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:1059:
+	 * If set to 0, then the firmware doesn’t support the advance CFA flow management

WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#472: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5457:
+	/* Indicates function ID that this event occured on. */

WARNING:LONG_LINE: line over 90 characters
#507: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5486:
+	#define HWRM_ASYNC_EVENT_CMPL_TCP_FLAG_ACTION_CHANGE_EVENT_ID_TCP_FLAG_ACTION_CHANGE \

WARNING:LONG_LINE: line over 90 characters
#510: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5489:
+		HWRM_ASYNC_EVENT_CMPL_TCP_FLAG_ACTION_CHANGE_EVENT_ID_TCP_FLAG_ACTION_CHANGE

WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#571: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5539:
+	/* Indicates the 2nd global id this event occured on. */

WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#628: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5575:
+	/* Indicates the 1st global id this event occured on. */

WARNING:TYPO_SPELLING: 'occured' may be misspelled - perhaps 'occurred'?
#648: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:5595:
+	 * Indicates EEM flow aging mode this event occured on. If

WARNING:LONG_LINE_COMMENT: line over 90 characters
#1763: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:24194:
+	/* IPV6 over virtual eXtensible Local Area Network with GPE header (IPV6oVXLANGPE) */

WARNING:LONG_LINE_COMMENT: line over 90 characters
#2332: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:27135:
+	/* Enhance Generic Routing Encapsulation (GRE version 1) inside IP datagram payload */

WARNING:LONG_LINE_COMMENT: line over 90 characters
#2336: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:27139:
+	/* IPV6 over virtual eXtensible Local Area Network with GPE header (IPV6oVXLANGPE) */

WARNING:LONG_LINE_COMMENT: line over 90 characters
#2379: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:27182:
+	/* Enhance Generic Routing Encapsulation (GRE version 1) inside IP datagram payload */

WARNING:LONG_LINE_COMMENT: line over 90 characters
#2385: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:27188:
+	/* IPV6 over virtual eXtensible Local Area Network with GPE header (IPV6oVXLANGPE) */

WARNING:LONG_LINE_COMMENT: line over 90 characters
#2545: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:27439:
+	 * flow table specified. This flag is set to 0 by older driver. For older firmware,

WARNING:LONG_LINE_COMMENT: line over 90 characters
#2552: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:27446:
+	 * context memory tables..etc.  This flag is set to 0 by older driver. For older firmware,

WARNING:LONG_LINE_COMMENT: line over 90 characters
#2874: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:28232:
+	/* Enhance Generic Routing Encapsulation (GRE version 1) inside IP datagram payload */

WARNING:LONG_LINE_COMMENT: line over 90 characters
#2883: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:28241:
+	/* IPV6 over virtual eXtensible Local Area Network with GPE header (IPV6oVXLANGPE) */

WARNING:LONG_LINE_COMMENT: line over 90 characters
#3310: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:28668:
+	 * The maximum number of entries supported by EEM.   When configuring the host memory

WARNING:LONG_LINE_COMMENT: line over 90 characters
#3313: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:28671:
+	 * Any value that are not these values, the FW will round down to the closest support

WARNING:LONG_LINE_COMMENT: line over 90 characters
#3388: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:28746:
+	 * Configured EEM with the given number of entries.  All the EEM tables KEY0, KEY1,

WARNING:LONG_LINE_COMMENT: line over 90 characters
#3389: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:28747:
+	 * RECORD, EFC all have the same number of entries and all tables will be configured

WARNING:LONG_LINE_COMMENT: line over 90 characters
#3661: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:29023:
+	 * Value of 1 to indicate that the firmware support flow reset all operation through

WARNING:LONG_LINE: line over 90 characters
#3674: FILE: drivers/net/bnxt/hsi_struct_def_dpdk.h:29034:
+	#define HWRM_CFA_ADV_FLOW_MGNT_QCAPS_OUTPUT_FLAGS_NTUPLE_FLOW_DEST_FUNC_SUPPORTED \

total: 0 errors, 22 warnings, 0 checks, 3630 lines checked

           reply	other threads:[~2019-05-29 15:04 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20190529150234.15166-8-lance.richardson@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=20190529150420.A50061B953@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=lance.richardson@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).