From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cavium-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id; bh=oqbgwo/XUHIGFQb2cA0wWXVxlPRV4FT6j5IqXS+4CIM=; b=zpW1+7La75cc8nMoAdmvRngIvaqtjYHEQ9QznRTkGIWxT0YnoVHRcbjyGNRFzENT81 AySHOEocSPuWMCJsuOESW8kUBN20v9FZO8m3rIUuj7BwXnf/AuHpZd+3xWNOiwFDFkaR 6FpsdW/EZsbmtpiyxyoHnkGKKlc07zYvMQhJAnWNEMtRTbDvRTg2oVrHQnCmuqlvtjjD SmGKxOUimsvXQIbb+vZi7BVVNCny3q9W1OYVfunVerRUBt8h1VQUiBjkHRSDLOUGowuk QZptPyCTuAYYUnajEnw47b4X7GLyOz4x9JwZBocEgWM7sQWphMdcTfp0Svy+L+w3V0Wb Gd0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=oqbgwo/XUHIGFQb2cA0wWXVxlPRV4FT6j5IqXS+4CIM=; b=WrzOuMY/mKck+5p8vwKDmpWDqiQQ1I5Gj3b6cYFSsxa7X9smJyOokqTC0VOltaLXU4 TR2reQh9cJMyvWVMsmfc+/d8/c4ObRyLVwvoR8IR6ebM3PBZK1zoptjgTc60efcRfHGI EbSAA7IwptF63876EFek5P/LWU0Ic9nMrTS0zpMK3kVZOY0BtWUSHWSKdpIzISkoUrv2 Fh9E5ZcVkZiZ4t9/XTLX3pcq1SOXEU9AIO4QVvd3n/MOAfEyQDICliwn6yAbG0UXoDqb nuANyd20EqSU/nNEkc0CY7Av2tKa6o7NNhq5g4dqgfgJ1PgsObruE3TBVxRm9a9HchL+ qJYQ== X-Gm-Message-State: AJaThX7jPgQhbpPB2/45IIzhrFpHiGwMb4hnAIv/j5c4nstZ/7gDRzks YOnkTNQdn2gzYaXIsVRSRM5am3Tj X-Google-Smtp-Source: AGs4zMaCYDBNQNyXYZqOzcsy0//OYLPnErc3mX/Ec+HfkPCCUckIHRJcyh1ns8wFFhLbvrjrF4fH7Q== X-Received: by 10.84.177.129 with SMTP id x1mr7097494plb.217.1512152948477; Fri, 01 Dec 2017 10:29:08 -0800 (PST) Received: from localhost.localdomain (c-73-41-93-56.hsd1.ca.comcast.net. [73.41.93.56]) by smtp.gmail.com with ESMTPSA id z2sm11703931pfh.39.2017.12.01.10.29.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Dec 2017 10:29:07 -0800 (PST) From: Roy Franz X-Google-Original-From: Roy Franz To: dev@dpdk.org Cc: Roy Franz Date: Fri, 1 Dec 2017 10:26:39 -0800 Message-Id: <20171201182640.21885-1-roy.franz@cavium.com> X-Mailer: git-send-email 2.11.0 Subject: [dpdk-dev] [PATCH 1/2] doc: Clarify wording regarding actions and flow rules. X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Dec 2017 18:29:10 -0000 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