DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>,
	David Marchand <david.marchand@redhat.com>,
	Ori Kam <orika@nvidia.com>, Guy Kaneti <guyk@marvell.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Rosen Xu <rosen.xu@intel.com>, Luca Boccassi <bluca@debian.org>
Subject: [dpdk-dev] [PATCH v2 5/7] doc: fix driver names in regex devices guide
Date: Tue,  3 Nov 2020 12:36:06 +0000	[thread overview]
Message-ID: <20201103123608.1114433-6-bruce.richardson@intel.com> (raw)
In-Reply-To: <20201103123608.1114433-1-bruce.richardson@intel.com>

Since the built driver filenames have changed in DPDK 20.11, we need to
update the driver doc to match.

Fixes: a20b2c01a7a1 ("build: standardize component names and defines")

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: David Marchand <david.marchand@redhat.com>
---
 doc/guides/regexdevs/mlx5.rst      | 4 ++--
 doc/guides/regexdevs/octeontx2.rst | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/guides/regexdevs/mlx5.rst b/doc/guides/regexdevs/mlx5.rst
index 0e6ee8ccfc..faaa6ac11d 100644
--- a/doc/guides/regexdevs/mlx5.rst
+++ b/doc/guides/regexdevs/mlx5.rst
@@ -7,7 +7,7 @@ MLX5 RegEx driver
 =================
 
 The MLX5 RegEx (Regular Expression) driver library
-(**librte_pmd_mlx5_regex**) provides support for **Mellanox BlueField 2**
+(**librte_regex_mlx5**) provides support for **Mellanox BlueField 2**
 families of 25/50/100/200 Gb/s adapters.
 
 Design
@@ -26,7 +26,7 @@ to get the best performances:
 - Direct Verbs is a device-specific API
 - DevX allows to access firmware objects
 
-Enabling librte_pmd_mlx5_regex causes DPDK applications to be linked against
+Enabling librte_regex_mlx5 causes DPDK applications to be linked against
 libibverbs.
 
 Mellanox mlx5 pci device can be probed by number of different pci devices,
diff --git a/doc/guides/regexdevs/octeontx2.rst b/doc/guides/regexdevs/octeontx2.rst
index 4ea800f949..b39d457d60 100644
--- a/doc/guides/regexdevs/octeontx2.rst
+++ b/doc/guides/regexdevs/octeontx2.rst
@@ -4,7 +4,7 @@
 OCTEON TX2 REE Regexdev Driver
 ==============================
 
-The OCTEON TX2 REE PMD (**librte_pmd_octeontx2_regex**) provides poll mode
+The OCTEON TX2 REE PMD (**librte_regex_octeontx2**) provides poll mode
 regexdev driver support for the inbuilt regex device found in the **Marvell OCTEON TX2**
 SoC family.
 
-- 
2.25.1


  parent reply	other threads:[~2020-11-03 12:38 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 17:44 [dpdk-dev] [PATCH 0/8] fix driver filenames in the docs Bruce Richardson
2020-11-02 17:45 ` [dpdk-dev] [PATCH 1/8] regex/octeontx2: fix unnecessary name override Bruce Richardson
2020-11-02 19:48   ` David Marchand
2020-11-03  0:30     ` Thomas Monjalon
2020-11-03  8:19       ` David Marchand
2020-11-03  9:06         ` Thomas Monjalon
2020-11-03  9:19           ` David Marchand
2020-11-03  9:45             ` David Marchand
2020-11-03 10:27               ` Bruce Richardson
2020-11-02 17:45 ` [dpdk-dev] [PATCH 2/8] doc: fix driver names in compression devices guide Bruce Richardson
2020-11-02 19:54   ` David Marchand
2020-11-02 17:45 ` [dpdk-dev] [PATCH 3/8] doc: fix driver names in crypto " Bruce Richardson
2020-11-02 20:00   ` David Marchand
2020-11-02 20:02     ` David Marchand
2020-11-03 10:28       ` Bruce Richardson
2020-11-02 17:45 ` [dpdk-dev] [PATCH 4/8] doc: fix driver names in event " Bruce Richardson
2020-11-02 20:03   ` David Marchand
2020-11-02 17:45 ` [dpdk-dev] [PATCH 5/8] doc: fix driver names in NIC " Bruce Richardson
2020-11-02 20:17   ` David Marchand
2020-11-02 20:45     ` David Marchand
2020-11-03  2:31   ` Xu, Rosen
2020-11-03  2:47     ` Ajit Khaparde
2020-11-02 17:45 ` [dpdk-dev] [PATCH 6/8] doc: fix driver names in regex " Bruce Richardson
2020-11-02 20:07   ` David Marchand
2020-11-02 17:45 ` [dpdk-dev] [PATCH 7/8] doc: fix driver names in vDPA " Bruce Richardson
2020-11-02 20:09   ` David Marchand
2020-11-02 17:45 ` [dpdk-dev] [PATCH 8/8] doc: fix driver names in programmers guide Bruce Richardson
2020-11-02 20:12   ` David Marchand
2020-11-02 20:19 ` [dpdk-dev] [PATCH 0/8] fix driver filenames in the docs David Marchand
2020-11-03 12:36 ` [dpdk-dev] [PATCH v2 0/7] " Bruce Richardson
2020-11-03 12:36   ` [dpdk-dev] [PATCH v2 1/7] doc: fix driver names in compression devices guide Bruce Richardson
2020-11-03 12:36   ` [dpdk-dev] [PATCH v2 2/7] doc: fix driver names in crypto " Bruce Richardson
2020-11-03 13:05     ` David Marchand
2020-11-03 12:36   ` [dpdk-dev] [PATCH v2 3/7] doc: fix driver names in event " Bruce Richardson
2020-11-03 12:36   ` [dpdk-dev] [PATCH v2 4/7] doc: fix driver names in NIC " Bruce Richardson
2020-11-03 12:36   ` Bruce Richardson [this message]
2020-11-03 12:36   ` [dpdk-dev] [PATCH v2 6/7] doc: fix driver names in vDPA " Bruce Richardson
2020-11-03 12:36   ` [dpdk-dev] [PATCH v2 7/7] doc: fix driver names in programmers guide Bruce Richardson
2020-11-03 14:50   ` [dpdk-dev] [PATCH v2 0/7] fix driver filenames in the docs David Marchand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201103123608.1114433-6-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=bluca@debian.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=guyk@marvell.com \
    --cc=orika@nvidia.com \
    --cc=rosen.xu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).