From: Ray Kinsella <mdr@ashroe.eu>
To: Sathesh B Edara <sedara@marvell.com>
Cc: sburla@marvell.com, jerinj@marvell.com,
Thomas Monjalon <thomas@monjalon.net>,
Nalla Pradeep <pnalla@marvell.com>,
Radha Mohan Chintakuntla <radhac@marvell.com>,
Veerasenareddy Burru <vburru@marvell.com>,
dev@dpdk.org
Subject: Re: [PATCH] drivers: rename octeon ep PMD
Date: Tue, 07 Jun 2022 15:38:40 +0100 [thread overview]
Message-ID: <87pmjkmtbk.fsf@mdr78.vserver.site> (raw)
In-Reply-To: <20220607141546.28848-1-sedara@marvell.com>
Sathesh B Edara <sedara@marvell.com> writes:
> This patch renames octeon end point driver from
> octeontx_ep to octeon_ep
>
> Signed-off-by: Sathesh B Edara <sedara@marvell.com>
> ---
> MAINTAINERS | 6 +-
> .../{octeontx_ep.ini => octeon_ep.ini} | 2 +-
> doc/guides/nics/index.rst | 2 +-
> .../nics/{octeontx_ep.rst => octeon_ep.rst} | 2 +-
> drivers/net/meson.build | 2 +-
> .../{octeontx_ep => octeon_ep}/meson.build | 0
> .../{octeontx_ep => octeon_ep}/otx2_ep_vf.c | 0
> .../{octeontx_ep => octeon_ep}/otx2_ep_vf.h | 0
> .../otx_ep_common.h | 0
> .../otx_ep_ethdev.c | 67 +++++++++++++++++++
> .../{octeontx_ep => octeon_ep}/otx_ep_rxtx.c | 0
> .../{octeontx_ep => octeon_ep}/otx_ep_rxtx.h | 0
> .../{octeontx_ep => octeon_ep}/otx_ep_vf.c | 0
> .../{octeontx_ep => octeon_ep}/otx_ep_vf.h | 0
> .../{octeontx_ep => octeon_ep}/version.map | 0
> 15 files changed, 74 insertions(+), 7 deletions(-)
> rename doc/guides/nics/features/{octeontx_ep.ini => octeon_ep.ini} (75%)
> rename doc/guides/nics/{octeontx_ep.rst => octeon_ep.rst} (93%)
> rename drivers/net/{octeontx_ep => octeon_ep}/meson.build (100%)
> rename drivers/net/{octeontx_ep => octeon_ep}/otx2_ep_vf.c (100%)
> rename drivers/net/{octeontx_ep => octeon_ep}/otx2_ep_vf.h (100%)
> rename drivers/net/{octeontx_ep => octeon_ep}/otx_ep_common.h (100%)
> rename drivers/net/{octeontx_ep => octeon_ep}/otx_ep_ethdev.c (86%)
> rename drivers/net/{octeontx_ep => octeon_ep}/otx_ep_rxtx.c (100%)
> rename drivers/net/{octeontx_ep => octeon_ep}/otx_ep_rxtx.h (100%)
> rename drivers/net/{octeontx_ep => octeon_ep}/otx_ep_vf.c (100%)
> rename drivers/net/{octeontx_ep => octeon_ep}/otx_ep_vf.h (100%)
> rename drivers/net/{octeontx_ep => octeon_ep}/version.map (100%)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index f34f6fa2e9..01c0c5ee5e 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -798,9 +798,9 @@ M: Nalla Pradeep <pnalla@marvell.com>
> M: Radha Mohan Chintakuntla <radhac@marvell.com>
> M: Veerasenareddy Burru <vburru@marvell.com>
> T: git://dpdk.org/next/dpdk-next-net-mrvl
> -F: drivers/net/octeontx_ep/
> -F: doc/guides/nics/features/octeontx_ep.ini
> -F: doc/guides/nics/octeontx_ep.rst
> +F: drivers/net/octeon_ep/
> +F: doc/guides/nics/features/octeon_ep.ini
> +F: doc/guides/nics/octeon_ep.rst
>
Straight forward rename,
Acked-by: Ray Kinsella <mdr@ashroe.eu>
next prev parent reply other threads:[~2022-06-07 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 14:15 Sathesh B Edara
2022-06-07 14:38 ` Ray Kinsella [this message]
2022-06-07 15:06 ` Thomas Monjalon
2022-06-07 16:18 ` [EXT] " Veerasenareddy Burru
2022-06-07 16:56 ` Thomas Monjalon
2022-06-08 5:33 ` Veerasenareddy Burru
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=87pmjkmtbk.fsf@mdr78.vserver.site \
--to=mdr@ashroe.eu \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pnalla@marvell.com \
--cc=radhac@marvell.com \
--cc=sburla@marvell.com \
--cc=sedara@marvell.com \
--cc=thomas@monjalon.net \
--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).