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 5F448A0093 for ; Wed, 9 Mar 2022 12:03:28 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5A7A340150; Wed, 9 Mar 2022 12:03:28 +0100 (CET) Received: from smtp-relay-internal-1.canonical.com (smtp-relay-internal-1.canonical.com [185.125.188.123]) by mails.dpdk.org (Postfix) with ESMTP id A8D5D410E8 for ; Wed, 9 Mar 2022 12:03:26 +0100 (CET) Received: from mail-ed1-f70.google.com (mail-ed1-f70.google.com [209.85.208.70]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-1.canonical.com (Postfix) with ESMTPS id 7E5753F7DF for ; Wed, 9 Mar 2022 11:03:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1646823805; bh=8CUc9JFNh/0t6kgJrwvcNOnlG2WcAfA8wz1imdcHWkM=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version; b=YF6U3GTM/Gz/7EF3rFOgNa4WeTqPAH3jncX8rRr/NMIOGZkXgNi5PteXnQdFn6lJ4 S5A14AXMBJpG7g4pI84iJhNZfXUNtyU1ScjsXbeagpZgxlpMhY0d2cGCTTVr+qHnud J3grdlNQ/h0SepzvMoqoXvpwc9kthQ98TXTQi4fLNSJsGMtCFJBvXJc+t7aEqKo9nP G/nhfxTF/s+I2ShSWYgnNF7p6mwEmw5toZiyGZDDl2Hc8AREMGN1hriJIrZpllsRjg 1mjNJven9wOJlMIzCxkvLthzj38Iy8wXFk+Dm6qNqKvU6w7NZzvnJELcpiTp8J9Xmw g02ZakQQFNzIg== Received: by mail-ed1-f70.google.com with SMTP id bd4-20020a056402206400b004162b6d8618so1060930edb.19 for ; Wed, 09 Mar 2022 03:03:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=8CUc9JFNh/0t6kgJrwvcNOnlG2WcAfA8wz1imdcHWkM=; b=GaTLXGaftlR9h8xxA2IKRpBh0Irzr/dEJhotH69YvFwuiCTicyNWka0011CSXirs9U anUpU565ZLkgOdfu+1BmuCJc5lIsVgZ7jzUL4lbveKUAgBEwS4D9O3EsdpJ5MfFWNqkj agdShbk2rVAxDS+RQ3Y+hOTxe8rYGhav2QOY6g0EarrQsBp4sa2GXkiRv706P6XN/0+w R60CMmTTar1GNmaCgsOZMWv5EzWVY/OecJ61yBHRgvg0dKzzVLqwzc6QrBFYotsRJVcR SZM/OXbNRW7TGMlhJcuRIsZIEBKzClLvilBjWdfg3hqzCJkiB1wssw4pNkzRNagkJ94V GHHw== X-Gm-Message-State: AOAM532LnyPMOdUOu4jtrYIOa4Lq6buEDFjb7lKudzRudHjZKbwv7H8Z RGQeBRs/HWbu6tj4hZK7d7Or0uReTL7q00ZdoI5FWeMjWruTBflW7k/TbmNftmrV7kVu5FM1zgN Z+r09WCZOaDOLP1nUo77tfUTf X-Received: by 2002:a17:906:b155:b0:6c9:ea2d:3363 with SMTP id bt21-20020a170906b15500b006c9ea2d3363mr16822398ejb.729.1646823804630; Wed, 09 Mar 2022 03:03:24 -0800 (PST) X-Google-Smtp-Source: ABdhPJzhrHlHd2TWKk64JDDIS0mWtTma1CdSwgZQ+ah4eDQp3m4tuKU31MLDFgkjvF3efjUuIIQUDQ== X-Received: by 2002:a17:906:b155:b0:6c9:ea2d:3363 with SMTP id bt21-20020a170906b15500b006c9ea2d3363mr16822381ejb.729.1646823804357; Wed, 09 Mar 2022 03:03:24 -0800 (PST) Received: from localhost.localdomain (068-133-067-156.ip-addr.inexio.net. [156.67.133.68]) by smtp.gmail.com with ESMTPSA id c1-20020a170906762100b006d00ae72b0csm568601ejn.221.2022.03.09.03.03.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 09 Mar 2022 03:03:23 -0800 (PST) From: christian.ehrhardt@canonical.com To: Ali Alnubani Cc: Ferruh Yigit , dpdk stable Subject: patch 'doc: fix typos and punctuation in flow API guide' has been queued to stable release 19.11.12 Date: Wed, 9 Mar 2022 12:01:09 +0100 Message-Id: <20220309110116.1295395-38-christian.ehrhardt@canonical.com> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20220309110116.1295395-1-christian.ehrhardt@canonical.com> References: <20220309110116.1295395-1-christian.ehrhardt@canonical.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Hi, FYI, your patch has been queued to stable release 19.11.12 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 03/11/22. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Queued patches are on a temporary branch at: https://github.com/cpaelzer/dpdk-stable-queue This queued commit can be viewed at: https://github.com/cpaelzer/dpdk-stable-queue/commit/61110e21bb39b82e94497211b6327385824c259f Thanks. Christian Ehrhardt --- >From 61110e21bb39b82e94497211b6327385824c259f Mon Sep 17 00:00:00 2001 From: Ali Alnubani Date: Tue, 1 Mar 2022 14:17:09 +0200 Subject: [PATCH] doc: fix typos and punctuation in flow API guide [ upstream commit 00373909c8f0377f03969eabf530293a7af9e23f ] This fixes typos and punctuation in the rte flow API guide. Fixes: 2f82d143fb31 ("ethdev: add group jump action") Fixes: 4d73b6fb9907 ("doc: add generic flow API guide") Signed-off-by: Ali Alnubani Acked-by: Ferruh Yigit --- doc/guides/prog_guide/rte_flow.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst index a254c81efa..ce19d94710 100644 --- a/doc/guides/prog_guide/rte_flow.rst +++ b/doc/guides/prog_guide/rte_flow.rst @@ -65,12 +65,12 @@ Flow rules can also be grouped, the flow rule priority is specific to the group they belong to. All flow rules in a given group are thus processed within the context of that group. Groups are not linked by default, so the logical hierarchy of groups must be explicitly defined by flow rules themselves in each -group using the JUMP action to define the next group to redirect too. Only flow -rules defined in the default group 0 are guarantee to be matched against, this +group using the JUMP action to define the next group to redirect to. Only flow +rules defined in the default group 0 are guaranteed to be matched against. This makes group 0 the origin of any group hierarchy defined by an application. Support for multiple actions per rule may be implemented internally on top -of non-default hardware priorities, as a result both features may not be +of non-default hardware priorities. As a result, both features may not be simultaneously available to applications. Considering that allowed pattern/actions combinations cannot be known in -- 2.35.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2022-03-09 11:57:45.333636157 +0100 +++ 0038-doc-fix-typos-and-punctuation-in-flow-API-guide.patch 2022-03-09 11:57:43.412938506 +0100 @@ -1 +1 @@ -From 00373909c8f0377f03969eabf530293a7af9e23f Mon Sep 17 00:00:00 2001 +From 61110e21bb39b82e94497211b6327385824c259f Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 00373909c8f0377f03969eabf530293a7af9e23f ] + @@ -10 +11,0 @@ -Cc: stable@dpdk.org @@ -19 +20 @@ -index f2deef95d8..588914b231 100644 +index a254c81efa..ce19d94710 100644 @@ -22 +23 @@ -@@ -60,12 +60,12 @@ Flow rules can also be grouped, the flow rule priority is specific to the +@@ -65,12 +65,12 @@ Flow rules can also be grouped, the flow rule priority is specific to the