From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AF6E8C433B4 for ; Thu, 8 Apr 2021 13:22:43 +0000 (UTC) Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by mail.kernel.org (Postfix) with ESMTP id 40A63610CA for ; Thu, 8 Apr 2021 13:22:43 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 40A63610CA Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 77E93140FC3; Thu, 8 Apr 2021 15:22:42 +0200 (CEST) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by mails.dpdk.org (Postfix) with ESMTP id 5F4D640138; Thu, 8 Apr 2021 15:22:40 +0200 (CEST) IronPort-SDR: Yrd6jNz4sWAxPMEiMvsNO3nn2V2kX/wJPasfKBHpLK+EPmSqQvXXtWMjdjbF2UGWVAuivyX6zS vOV70VhCbJIQ== X-IronPort-AV: E=McAfee;i="6000,8403,9948"; a="193079160" X-IronPort-AV: E=Sophos;i="5.82,206,1613462400"; d="scan'208";a="193079160" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Apr 2021 06:22:39 -0700 IronPort-SDR: XmfFbHdOUHQMeLl6CP7HqFgzAu55WuR0mh62bjZuWkVY4q7IgmKfZx5J+tSsNFDXst6NZFY73Z JAAlzKOzDGNw== X-IronPort-AV: E=Sophos;i="5.82,206,1613462400"; d="scan'208";a="380249320" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.203.5]) ([10.213.203.5]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Apr 2021 06:22:37 -0700 To: Alexander Kozyrev , dev@dpdk.org Cc: stable@dpdk.org, rasland@nvidia.com, viacheslavo@nvidia.com References: <20210331160028.21811-1-akozyrev@nvidia.com> <20210408123258.10452-1-akozyrev@nvidia.com> From: Ferruh Yigit X-User: ferruhy Message-ID: Date: Thu, 8 Apr 2021 14:22:34 +0100 MIME-Version: 1.0 In-Reply-To: <20210408123258.10452-1-akozyrev@nvidia.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v2] doc: refer to the supported Field IDs for modify field 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" On 4/8/2021 1:32 PM, Alexander Kozyrev wrote: > Fix the documentation about the MODIFY_FIELD RTE Flow action. > 1. Include the rte_flow_field_id enumeration reference to point > to the full list of all supported Field IDs available. > 2. Correct the formatting of the MODIFY_FIELD action and the > destination/source field definition tables. > > Fixes: 73b68f4c54 ("ethdev: introduce generic modify flow action") > Cc: stable@dpdk.org > > Signed-off-by: Alexander Kozyrev > Acked-by: Viacheslav Ovsiienko Reviewed-by: Ferruh Yigit Applied to dpdk-next-net/main, thanks.