From patchwork Wed Jan 30 11:20:18 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Thomas Monjalon X-Patchwork-Id: 50091 X-Patchwork-Delegate: thomas@monjalon.net Return-Path: X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id CAA8C1B2AB; Wed, 30 Jan 2019 12:20:45 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 5B5511B20C for ; Wed, 30 Jan 2019 12:20:44 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 063DF2314F; Wed, 30 Jan 2019 06:20:44 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 30 Jan 2019 06:20:44 -0500 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; s=mesmtp; bh=mf8Rtk3VS4 FKn43sRLuh4u52YrvfcYEEE7h6GO4Y7l0=; b=AoffdqSWuamh/tU1BfFarqX7Ri 2SqATnXu2vUKl7J3Jjxwy5Oa1Bexl2yUfwPoHuJZdfrLikDgKMi483+JPmJpEVcU Fs4Y0e59QCSiNpxncxOS+4f6uybycz+3nzs76OtUgSkKA99Lk7f5NEHnq8DvyVGa NhMljFydeUzXLxYyo= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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= fm1; bh=mf8Rtk3VS4FKn43sRLuh4u52YrvfcYEEE7h6GO4Y7l0=; b=Al3wWJGq sLCTGjBTXIPVSiV/1jQCeCtFglyC+A54RThNCV5xUlKF8rmrXrcahHVa3aK5YoMV qXBMYyPi1RFGJ4fVnyJdNcXSoY0o9ng6KDIoNBqZC6nLHcJ9WsET9/WZVCWNCK38 HiXn5OIe84pXqJWGN2CV5NsAX7YcGgcVL0u2ZwqFi1sx82+7pnlroPDBquP8RVGy HN7QgAZ9G3G8GXr1cAY979yNj8rUcNl9LCUp0dopbwdQFisE+ampMs1JR2RjFK0r 6QKX0vD+FoXf34vZFNuKNfRz2dLz5bcPExSzUqUqe3kUaRZw0oKLzXZf4B1ixjA3 RQPcPWSARstXig== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrjeeggddviecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffkffojg hfggfgsedtkeertdertddtnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceo thhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukfhppeejjedrudefgedrvddtfe drudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.monjalon.net (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 496AFE4650; Wed, 30 Jan 2019 06:20:41 -0500 (EST) From: Thomas Monjalon To: john.mcnamara@intel.com, marko.kovacevic@intel.com, shahafs@mellanox.com, yskoh@mellanox.com, Tomasz Duszynski , Dmitri Epshtein , Natalie Samsonov , Adrien Mazarguil Cc: dev@dpdk.org Date: Wed, 30 Jan 2019 12:20:18 +0100 Message-Id: <20190130112020.871-2-thomas@monjalon.net> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190130112020.871-1-thomas@monjalon.net> References: <20190130112020.871-1-thomas@monjalon.net> MIME-Version: 1.0 Subject: [dpdk-dev] [PATCH 1/3] doc: remove useless anchor for flow API guide 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" A doc page (.rst file) can be referenced with :doc: syntax instead of :ref: to .. anchor. Signed-off-by: Thomas Monjalon --- doc/guides/howto/rte_flow.rst | 2 +- doc/guides/nics/mvpp2.rst | 2 +- doc/guides/prog_guide/rte_flow.rst | 2 -- doc/guides/rel_notes/release_17_02.rst | 3 +-- 4 files changed, 3 insertions(+), 6 deletions(-) diff --git a/doc/guides/howto/rte_flow.rst b/doc/guides/howto/rte_flow.rst index 6a8534d98..3dcda6cb1 100644 --- a/doc/guides/howto/rte_flow.rst +++ b/doc/guides/howto/rte_flow.rst @@ -8,7 +8,7 @@ This document demonstrates some concrete examples for programming flow rules with the ``rte_flow`` APIs. * Detail of the rte_flow APIs can be found in the following link: - :ref:`Generic flow API ` . + :doc:`../prog_guide/rte_flow`. * Details of the TestPMD commands to set the flow rules can be found in the following link: :ref:`TestPMD Flow rules ` diff --git a/doc/guides/nics/mvpp2.rst b/doc/guides/nics/mvpp2.rst index b2ddeab50..9dcb93dd9 100644 --- a/doc/guides/nics/mvpp2.rst +++ b/doc/guides/nics/mvpp2.rst @@ -410,7 +410,7 @@ Flow API PPv2 offers packet classification capabilities via classifier engine which can be configured via generic flow API offered by DPDK. -For an additional description please refer to DPDK :ref:`Generic flow API `. +For an additional description please refer to DPDK :doc:`../prog_guide/rte_flow`. Supported flow actions ~~~~~~~~~~~~~~~~~~~~~~ diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst index dbf4999aa..472dcef47 100644 --- a/doc/guides/prog_guide/rte_flow.rst +++ b/doc/guides/prog_guide/rte_flow.rst @@ -2,8 +2,6 @@ Copyright 2016 6WIND S.A. Copyright 2016 Mellanox Technologies, Ltd -.. _Generic_flow_API: - Generic flow API (rte_flow) =========================== diff --git a/doc/guides/rel_notes/release_17_02.rst b/doc/guides/rel_notes/release_17_02.rst index d6c1c5670..2244d27f9 100644 --- a/doc/guides/rel_notes/release_17_02.rst +++ b/doc/guides/rel_notes/release_17_02.rst @@ -77,8 +77,7 @@ New Features higher-level than the legacy filtering framework, which it encompasses and supersedes (including all functions and filter types) . - See the :ref:`Generic flow API ` documentation for more - information. + See the :doc:`../prog_guide/rte_flow` documentation for more information. * **Added firmware version get API.**