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 5A7ECA0547; Wed, 29 Sep 2021 10:20:45 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D273040E3C; Wed, 29 Sep 2021 10:20:44 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id E6D184068F for ; Wed, 29 Sep 2021 10:20:43 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 807795C0209; Wed, 29 Sep 2021 04:20:43 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 29 Sep 2021 04:20:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= 1Wg+WENY9QpiDvSll8zR+tmrhScMPahOeTdjH0d1xhc=; b=Zx5hSbecYTMfk0HX 5PgL/IbAfKSQ/4NpdJ+IrSAszMxF3bWYA3Sg8NEi+R2co3IBhLHcRyD2gkvlTD3L 8vH9XsggGygfwuJ7MXPF7sc42D9FdzQsLV6ROizSydqiHC+NSVA6upyF1RYCTna5 H2H9/JRe1f9nlvK3TzlrXpEYmQ1/xvsmV2zwE0TnPfYrsyB87H2y/TlbSV5Svyj9 1Av05UoVdBNK2FR0zky6kiABf5dS96ECGbozUIy68cH2L6a7DDtGaMLiNVuM+91W oPJYDdijQhTbr58pAg5gXViwiYQsl7W/M4YhTXWwcKLtixQjW2NUAahnDk2tQ11y mWhGQA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=1Wg+WENY9QpiDvSll8zR+tmrhScMPahOeTdjH0d1x hc=; b=EdTNtGisJvQgwjCZRwiR3Esd3Dvc+FeCMSEa8FdkeF9nFZRFabxtOn9jF Ot7R8fCdzdTsToN05/CVzp1Y2ka08Oiux9fwHTcMdfdVWRF2vMGEgSTSxmqJTGuU h6VxHwx7JfQVhk5D1ZrtNGaw83sVGjU0gYqJ29VeHMbVfVZ5JSlctVmmmX1CBhVl KRcai54E8w6OBVLaU5QY2Zfno4COpoVW2QJRJJM/BmsjFCMs8CY3dcOTb/iBZYHm snIbmROt8FK/hAOCeAkCvVqaLKVMrOPE1ZNFhKgyP0OkXFN1Uh3sGIX4c/GpzJRf IfNP2Bt8HLGE1kIXU52nQxtKtpBCg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudekvddgtdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 29 Sep 2021 04:20:42 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit , Ajit Khaparde Cc: Venkat Duvvuru , dpdk-dev , Kishore Padmanabha , "jerinj@marvell.com" Date: Wed, 29 Sep 2021 10:20:40 +0200 Message-ID: <1971997.DethVJQmbG@thomas> In-Reply-To: References: <20210908050643.9989-1-venkatkumar.duvvuru@broadcom.com> <043f9e39-222d-975d-d361-f9b27e7a3c74@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v4 06/13] net/bnxt: add support for tunnel offload API X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 28/09/2021 23:32, Ajit Khaparde: > On Tue, Sep 28, 2021 at 5:43 AM Ferruh Yigit wrote: > > Following warning is reported by Jerin & Thomas: > > > > $ ./devtools/check-doc-vs-code.sh > > rte_flow doc out of sync for bnxt > > action shared > > > > > > This is mainly saying 'RTE_FLOW_ACTION_TYPE_SHARED' flow action is supported but > > not documented. But from code I am not sure if shared action is used, there is > > only one range check using this enum in the code, can you please clarify? > > Correct. RTE_FLOW_ACTION_TYPE_SHARED is being used only for a range check. > It is not really a supported action right now as far as the code is concerned. > As of now, no document update is necessary. Thanks You need to update something to make the check OK. If it is a false positive, it can be handled in the script, but we cannot let the script returning an error.