From: Veerasenareddy Burru <vburru@marvell.com>
To: Ray Kinsella <mdr@ashroe.eu>
Cc: <dev@dpdk.org>, Veerasenareddy Burru <vburru@marvell.com>
Subject: [PATCH] doc: announce rename of octeontx_ep driver
Date: Thu, 30 Jun 2022 11:55:32 -0700 [thread overview]
Message-ID: <20220630185532.29389-1-vburru@marvell.com> (raw)
To enable single unified driver to support current OcteonTx and
future Octeon PCI endpoint NICs, octeontx_ep driver is renamed to
octeon_ep to reflect common driver for all Octeon based
PCI endpoint NICs.
Signed-off-by: Veerasenareddy Burru <vburru@marvell.com>
---
doc/guides/rel_notes/deprecation.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 4e5b23c53d..d50e68aed4 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -125,3 +125,12 @@ Deprecation Notices
applications should be updated to use the ``dmadev`` library instead,
with the underlying HW-functionality being provided by the ``ioat`` or
``idxd`` dma drivers
+
+* drivers/octeontx_ep: rename octeontx_ep drivers
+
+ Current driver name "octeontx_ep" was to support OcteonTX line of products.
+ This is renamed to apply for all Octeon EP products:
+ OcteonTX + future Octeon chipsets.
+ This deprecation notice is to do following actions in DPDK v22.11 version.
+
+ #. Rename ``drivers/net/octeontx_ep/`` to ``drivers/net/octeon_ep/``
--
2.36.0
next reply other threads:[~2022-07-01 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 18:55 Veerasenareddy Burru [this message]
2022-07-11 15:01 ` Jerin Jacob
2022-07-12 14:09 ` Thomas Monjalon
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=20220630185532.29389-1-vburru@marvell.com \
--to=vburru@marvell.com \
--cc=dev@dpdk.org \
--cc=mdr@ashroe.eu \
/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).