From: Thomas Monjalon <thomas@monjalon.net>
To: Sathesh B Edara <sedara@marvell.com>,
Veerasenareddy Burru <vburru@marvell.com>
Cc: Ray Kinsella <mdr@ashroe.eu>,
Satananda Burla <sburla@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Pradeep Kumar Nalla <pnalla@marvell.com>,
Radha Chintakuntla <radhac@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
david.marchand@redhat.com
Subject: Re: [EXT] Re: [PATCH] drivers: rename octeon ep PMD
Date: Tue, 07 Jun 2022 18:56:19 +0200 [thread overview]
Message-ID: <12967340.rMLUfLXkoz@thomas> (raw)
In-Reply-To: <BYAPR18MB242364010D77EAB629F4B2D5CCA59@BYAPR18MB2423.namprd18.prod.outlook.com>
07/06/2022 18:18, Veerasenareddy Burru:
> From: Thomas Monjalon <thomas@monjalon.net>
> > 07/06/2022 16:38, Ray Kinsella:
> > > 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>
> > >
> > > Straight forward rename,
> > >
> > > Acked-by: Ray Kinsella <mdr@ashroe.eu>
> >
> > The name change was not announced.
> > Why is it required?
> Thomas,
> we acknowledge, missed to announce before submitting the change.
> Current driver name "octeontx_ep" was to support OcteonTX line of products. We are renaming it to apply for all Octeon EP products (OcteonTX + future Octeon chipsets).
Do you want to announce it first and do the change in 22.11?
It would allow users to be prepared for the change.
next prev parent reply other threads:[~2022-06-07 16:56 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
2022-06-07 15:06 ` Thomas Monjalon
2022-06-07 16:18 ` [EXT] " Veerasenareddy Burru
2022-06-07 16:56 ` Thomas Monjalon [this message]
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=12967340.rMLUfLXkoz@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mdr@ashroe.eu \
--cc=pnalla@marvell.com \
--cc=radhac@marvell.com \
--cc=sburla@marvell.com \
--cc=sedara@marvell.com \
--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).