From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <test-report-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 599F9A0C44
	for <public@inbox.dpdk.org>; Mon, 14 Jun 2021 17:13:46 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 51D884067E;
	Mon, 14 Jun 2021 17:13:46 +0200 (CEST)
Received: from dpdk.org (dpdk.org [92.243.24.197])
 by mails.dpdk.org (Postfix) with ESMTP id B0F264067A
 for <test-report@dpdk.org>; Mon, 14 Jun 2021 17:13:45 +0200 (CEST)
Received: by dpdk.org (Postfix, from userid 65534)
 id A51F1121198; Mon, 14 Jun 2021 17:13:45 +0200 (CEST)
In-Reply-To: <20210613000652.28191-50-ajit.khaparde@broadcom.com>
References: <20210613000652.28191-50-ajit.khaparde@broadcom.com>
To: test-report@dpdk.org
From: checkpatch@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
Message-Id: <20210614151345.A51F1121198@dpdk.org>
Date: Mon, 14 Jun 2021 17:13:45 +0200 (CEST)
Subject: [dpdk-test-report] |WARNING| pw94176 [PATCH v2 49/58] net/bnxt: add
 field opcodes in ULP
X-BeenThere: test-report@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: automatic DPDK test reports <test-report.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/test-report>,
 <mailto:test-report-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/test-report/>
List-Post: <mailto:test-report@dpdk.org>
List-Help: <mailto:test-report-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/test-report>,
 <mailto:test-report-request@dpdk.org?subject=subscribe>
Errors-To: test-report-bounces@dpdk.org
Sender: "test-report" <test-report-bounces@dpdk.org>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#10984: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:1300:
+		ULP_WP_SYM_DECAP_FUNC_THRU_TUN},

WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#11296: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:1571:
+		ULP_WP_SYM_DECAP_FUNC_THRU_TUN},

WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#12467: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:2526:
+		ULP_WP_SYM_DECAP_FUNC_THRU_TL2},

WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#12762: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:2770:
+		ULP_WP_SYM_DECAP_FUNC_THRU_TL2},

WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#14238: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:3991:
+		ULP_WP_SYM_DECAP_FUNC_THRU_TL2},

WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'?
#14533: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_wh_plus_act.c:4235:
+		ULP_WP_SYM_DECAP_FUNC_THRU_TL2},

total: 0 errors, 6 warnings, 0 checks, 30877 lines checked