From: Jerin Jacob <jerinjacobk@gmail.com>
To: Veerasenareddy Burru <vburru@marvell.com>
Cc: Ray Kinsella <mdr@ashroe.eu>, dpdk-dev <dev@dpdk.org>
Subject: Re: [PATCH v2] doc: announce rename of octeontx_ep driver
Date: Wed, 13 Jul 2022 14:58:44 +0530 [thread overview]
Message-ID: <CALBAE1MCXUhEXnJ8JQ68rrvz05X+TvUAnvb4ScLhnYgxzZjbJg@mail.gmail.com> (raw)
In-Reply-To: <20220713080857.28038-1-vburru@marvell.com>
On Wed, Jul 13, 2022 at 1:41 PM Veerasenareddy Burru <vburru@marvell.com> wrote:
>
> To enable single unified driver to support current OcteonTx and
> future Octeon PCI endpoint NICs, octeontx_ep driver will be renamed
> to octeon_ep to reflect common driver for all Octeon based
> PCI endpoint NICs.
>
> Signed-off-by: Veerasenareddy Burru <vburru@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
> ---
> v2 - reworded the announcement as per review comment.
>
> doc/guides/rel_notes/deprecation.rst | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 4e5b23c53d..63c6dac5e5 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -125,3 +125,9 @@ 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 driver
> +
> + Current driver name ``octeontx_ep`` was to support OcteonTX line of products.
> + It will be renamed to ``octeon_ep`` in DPDK 22.11 to apply for all
> + Octeon EP products: OcteonTX + future Octeon chipsets.
> --
> 2.36.0
>
next prev parent reply other threads:[~2022-07-13 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 8:08 Veerasenareddy Burru
2022-07-13 9:28 ` Jerin Jacob [this message]
2022-07-16 17:03 ` 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=CALBAE1MCXUhEXnJ8JQ68rrvz05X+TvUAnvb4ScLhnYgxzZjbJg@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=mdr@ashroe.eu \
--cc=vburru@marvell.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).