DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Veerasenareddy Burru <vburru@marvell.com>
Cc: Sathesh B Edara <sedara@marvell.com>,
	Satananda Burla <sburla@marvell.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	 Radha Chintakuntla <radhac@marvell.com>,
	Ray Kinsella <mdr@ashroe.eu>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v2 1/3] net: rename octeon ep PMD
Date: Fri, 19 Aug 2022 17:48:11 +0530	[thread overview]
Message-ID: <CALBAE1OkicjcYijWrGO=973BBUAmkbtPf5cAYVLUJqZEAHmkGw@mail.gmail.com> (raw)
In-Reply-To: <BYAPR18MB24235C4960E0ECB678D8B332CC6B9@BYAPR18MB2423.namprd18.prod.outlook.com>

On Tue, Aug 16, 2022 at 11:05 AM Veerasenareddy Burru
<vburru@marvell.com> wrote:
>
>
>
> > -----Original Message-----
> > From: Sathesh Edara <sedara@marvell.com>
> > Sent: Wednesday, July 27, 2022 2:22 AM
> > To: Satananda Burla <sburla@marvell.com>; Jerin Jacob Kollanukkaran
> > <jerinj@marvell.com>; Sathesh B Edara <sedara@marvell.com>; Thomas
> > Monjalon <thomas@monjalon.net>; Radha Chintakuntla
> > <radhac@marvell.com>; Veerasenareddy Burru <vburru@marvell.com>; Ray
> > Kinsella <mdr@ashroe.eu>
> > Cc: dev@dpdk.org
> > Subject: [PATCH v2 1/3] net: rename octeon ep PMD

Suggestion:
net/octeontx_ep: rename as octeon_ep


Also missed to update doc/guides/rel_notes/deprecation.rst
[for-next-net][dpdk-next-net-mrvl] $ git grep octeontx_ep
doc/guides/rel_notes/deprecation.rst:* net/octeontx_ep: The driver
``octeontx_ep`` was to support OCTEON TX

> >
> > This patch renames octeon end point driver from octeontx_ep to octeon_ep
> > to enable single unified driver to support current OcteonTx and future
> > Octeon PCI endpoint NICs to reflect common driver for all Octeon based PCI
> > endpoint NICs.
> >
> > Signed-off-by: Sathesh Edara <sedara@marvell.com>

> > rename from drivers/net/octeontx_ep/version.map
> > rename to drivers/net/octeon_ep/version.map
> Ack

When Acking please use full syntax: Acked-by: ...


Rest looks good to me.


> > --
> > 2.36.1
>

  reply	other threads:[~2022-08-19 12:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27  9:21 [PATCH v2 0/3] net/octeon_ep: rename driver and add features Sathesh Edara
2022-07-27  9:21 ` [PATCH v2 1/3] net: rename octeon ep PMD Sathesh Edara
2022-08-16  5:32   ` Veerasenareddy Burru
2022-08-19 12:18     ` Jerin Jacob [this message]
2022-08-22  9:10   ` [PATCH v3 0/3] net/octeon_ep: rename driver and add features Sathesh Edara
2022-08-22  9:10     ` [PATCH v3 1/3] net/octeontx_ep: rename as octeon_ep Sathesh Edara
2022-08-22  9:10     ` [PATCH v3 2/3] net/octeon_ep: support basic stats Sathesh Edara
2022-08-22  9:10     ` [PATCH v3 3/3] net/octeon_ep: support link status Sathesh Edara
2022-08-23  5:50     ` [EXT] [PATCH v3 0/3] net/octeon_ep: rename driver and add features Veerasenareddy Burru
2022-08-27 12:24       ` Jerin Jacob
2022-07-27  9:21 ` [PATCH v2 2/3] net/octeon_ep: support basic stats Sathesh Edara
2022-08-16  5:34   ` Veerasenareddy Burru
2022-07-27  9:21 ` [PATCH v2 3/3] net/octeon_ep: support link status Sathesh Edara
2022-08-16  5:34   ` 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='CALBAE1OkicjcYijWrGO=973BBUAmkbtPf5cAYVLUJqZEAHmkGw@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=mdr@ashroe.eu \
    --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).