From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 324B8A04B1 for ; Wed, 4 Nov 2020 14:00:50 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 0ED03C944; Wed, 4 Nov 2020 14:00:49 +0100 (CET) Received: by dpdk.org (Postfix, from userid 1017) id 771E7C93A; Wed, 4 Nov 2020 14:00:47 +0100 (CET) In-Reply-To: <20201104125918.9751-3-orika@nvidia.com> References: <20201104125918.9751-3-orika@nvidia.com> To: test-report@dpdk.org Cc: Ori Kam Message-Id: <20201104130047.771E7C93A@dpdk.org> Date: Wed, 4 Nov 2020 14:00:47 +0100 (CET) From: checkpatch@dpdk.org Subject: [dpdk-test-report] |WARNING| pw83680 [PATCH v2 2/2] ethdev: introduce sft lib X-BeenThere: test-report@dpdk.org X-Mailman-Version: 2.1.15 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/83680 _coding style issues_ WARNING:TYPO_SPELLING: 'privious' may be misspelled - perhaps 'previous'? #56: privious or future packets. WARNING:TYPO_SPELLING: 'returend' may be misspelled - perhaps 'returned'? #116: which will result in the flow-id returend to the application WARNING:TYPO_SPELLING: 'attache' may be misspelled - perhaps 'attaché'? #348: FILE: lib/librte_ethdev/rte_sft.h:145: + * - action SFT: retrieve SFT flow context and attache it to the processed WARNING:TYPO_SPELLING: 'sate' may be misspelled - perhaps 'state'? #356: FILE: lib/librte_ethdev/rte_sft.h:153: + * undefined sate attached to the packet meaning that the flow is not WARNING:TYPO_SPELLING: 'sate' may be misspelled - perhaps 'state'? #383: FILE: lib/librte_ethdev/rte_sft.h:180: + * - analyze user-defined flow state and CT state (see state & ct_sate fields WARNING:TYPO_SPELLING: 'Incase' may be misspelled - perhaps 'In case'? #713: FILE: lib/librte_ethdev/rte_sft.h:510: + * Incase the mbuf is out of order or fragmented the mbuf_out will be NULL. WARNING:TYPO_SPELLING: 'allways' may be misspelled - perhaps 'always'? #716: FILE: lib/librte_ethdev/rte_sft.h:513: + * consumed and the mbuf_out will allways be NULL. WARNING:TYPO_SPELLING: 'destory' may be misspelled - perhaps 'destroy'? #1221: FILE: lib/librte_ethdev/rte_sft_driver.h:134: +typedef int *(*sft_entry_destory_t)(struct rte_eth_dev *dev, WARNING:TYPO_SPELLING: 'destory' may be misspelled - perhaps 'destroy'? #1264: FILE: lib/librte_ethdev/rte_sft_driver.h:177: + sft_entry_destory_t sft_entry_destory; WARNING:TYPO_SPELLING: 'destory' may be misspelled - perhaps 'destroy'? #1264: FILE: lib/librte_ethdev/rte_sft_driver.h:177: + sft_entry_destory_t sft_entry_destory; total: 0 errors, 10 warnings, 1128 lines checked