From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C8D46A0524 for ; Tue, 1 Jun 2021 09:45:13 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2FBC3410F7; Tue, 1 Jun 2021 09:45:13 +0200 (CEST) Received: from dpdk.org (dpdk.org [92.243.24.197]) by mails.dpdk.org (Postfix) with ESMTP id 3B5C0410E3 for ; Tue, 1 Jun 2021 09:45:12 +0200 (CEST) Received: by dpdk.org (Postfix, from userid 65534) id 1EC19120C04; Tue, 1 Jun 2021 09:45:12 +0200 (CEST) In-Reply-To: <20210530085929.29695-35-venkatkumar.duvvuru@broadcom.com> References: <20210530085929.29695-35-venkatkumar.duvvuru@broadcom.com> To: test-report@dpdk.org From: checkpatch@dpdk.org Cc: Venkat Duvvuru Message-Id: <20210601074512.1EC19120C04@dpdk.org> Date: Tue, 1 Jun 2021 09:45:12 +0200 (CEST) Subject: [dpdk-test-report] |WARNING| pw93692 [PATCH 34/58] net/bnxt: add support for conflict resolution X-BeenThere: test-report@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: automatic DPDK test reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: test-report-bounces@dpdk.org Sender: "test-report" Test-Label: checkpatch Test-Status: WARNING http://dpdk.org/patch/93692 _coding style issues_ WARNING:TYPO_SPELLING: 'indentify' may be misspelled - perhaps 'identify'? #2472: FILE: drivers/net/bnxt/tf_ulp/ulp_rte_parser.c:626: +/* Internal Function to indentify broadcast or multicast packets */ WARNING:TYPO_SPELLING: 'seting' may be misspelled - perhaps 'setting'? #2502: FILE: drivers/net/bnxt/tf_ulp/ulp_rte_parser.c:767: + * The priortiy field is ignored since OVS is seting it as WARNING:TYPO_SPELLING: 'seting' may be misspelled - perhaps 'setting'? #2522: FILE: drivers/net/bnxt/tf_ulp/ulp_rte_parser.c:963: + * The tos field is ignored since OVS is seting it as wild card WARNING:TYPO_SPELLING: 'lable' may be misspelled - perhaps 'label'? #2546: FILE: drivers/net/bnxt/tf_ulp/ulp_rte_parser.c:1108: + * The TC and flow lable field are ignored since OVS is seting WARNING:TYPO_SPELLING: 'seting' may be misspelled - perhaps 'setting'? #2546: FILE: drivers/net/bnxt/tf_ulp/ulp_rte_parser.c:1108: + * The TC and flow lable field are ignored since OVS is seting WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'? #8681: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:666: + BNXT_ULP_WH_PLUS_SYM_DECAP_FUNC_THRU_TL2 = 3, WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'? #8682: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:667: + BNXT_ULP_WH_PLUS_SYM_DECAP_FUNC_THRU_TL3 = 8, WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'? #8683: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:668: + BNXT_ULP_WH_PLUS_SYM_DECAP_FUNC_THRU_TL4 = 9, WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'? #8684: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:669: + BNXT_ULP_WH_PLUS_SYM_DECAP_FUNC_THRU_TUN = 10, WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'? #8685: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:670: + BNXT_ULP_WH_PLUS_SYM_DECAP_FUNC_THRU_L2 = 11, WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'? #8686: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:671: + BNXT_ULP_WH_PLUS_SYM_DECAP_FUNC_THRU_L3 = 12, WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'? #8687: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:672: + BNXT_ULP_WH_PLUS_SYM_DECAP_FUNC_THRU_L4 = 13, WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'? #8899: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:884: + BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_TL2 = 3, WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'? #8900: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:885: + BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_TL3 = 8, WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'? #8901: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:886: + BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_TL4 = 9, WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'? #8902: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:887: + BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_TUN = 10, WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'? #8903: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:888: + BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_L2 = 11, WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'? #8904: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:889: + BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_L3 = 12, WARNING:TYPO_SPELLING: 'THRU' may be misspelled - perhaps 'THROUGH'? #8905: FILE: drivers/net/bnxt/tf_ulp/ulp_template_db_enum.h:890: + BNXT_ULP_STINGRAY_SYM_DECAP_FUNC_THRU_L4 = 13, WARNING:TYPO_SPELLING: 'resoution' may be misspelled - perhaps 'resolution'? #80039: FILE: drivers/net/bnxt/tf_ulp/ulp_template_struct.h:221: + /* conflict resoution opcode */ total: 0 errors, 20 warnings, 0 checks, 80177 lines checked