From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roy Franz Subject: [PATCH 1/2] doc: Clarify wording regarding actions and flow rules. Date: Fri, 1 Dec 2017 10:26:39 -0800 Message-ID: <20171201182640.21885-1-roy.franz@cavium.com> Cc: Roy Franz To: dev@dpdk.org Return-path: Received: from mail-pl0-f66.google.com (mail-pl0-f66.google.com [209.85.160.66]) by dpdk.org (Postfix) with ESMTP id EE2B63256 for ; Fri, 1 Dec 2017 19:29:09 +0100 (CET) Received: by mail-pl0-f66.google.com with SMTP id i6so6720751plt.13 for ; Fri, 01 Dec 2017 10:29:09 -0800 (PST) List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Current wording regarding actions and flow rules doesn't make sense. Signed-off-by: Roy Franz --- Maybe a better word than 'assigned' could be chosen? (attached, associated with, etc) I'm happy to spin this if needed. doc/guides/prog_guide/rte_flow.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst index d158be5e4..9de6d32d3 100644 --- a/doc/guides/prog_guide/rte_flow.rst +++ b/doc/guides/prog_guide/rte_flow.rst @@ -984,7 +984,7 @@ Actions ~~~~~~~ Each possible action is represented by a type. Some have associated -configuration structures. Several actions combined in a list can be affected +configuration structures. Several actions combined in a list can be assigned to a flow rule. That list is not ordered. They fall in three categories: -- 2.11.0