From: Ferruh Yigit <ferruh.yigit@intel.com>
To: <jerinj@marvell.com>, Ray Kinsella <mdr@ashroe.eu>
Cc: <dev@dpdk.org>, <thomas@monjalon.net>, <adwivedi@marvell.com>,
<anoobj@marvell.com>, <lironh@marvell.com>,
<pbhagavatula@marvell.com>, <ndabilpuram@marvell.com>,
<kirankumark@marvell.com>, <gakhil@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] doc: deprecation notice to remove octeontx2 drivers
Date: Tue, 9 Nov 2021 15:58:50 +0000 [thread overview]
Message-ID: <c8c32cb1-a06d-60c4-6bb3-de42217e381f@intel.com> (raw)
In-Reply-To: <20211109155132.3515275-1-jerinj@marvell.com>
On 11/9/2021 3:51 PM, jerinj@marvell.com wrote:
> From: Jerin Jacob<jerinj@marvell.com>
>
> In the view of enabling unified driver for octeontx2(cn9k)/
> octeontx3(cn10k), removing drivers/octeontx2 drivers and
> replace with drivers/cnxk/ which supports both octeontx2(cn9k)
> and octeontx3(cn10k) SoCs.
>
> This deprecation notice is to do following actions in DPDK v22.02
> version.
> - Replace drivers/common/octeontx2/ with drivers/common/cnxk/
> - Replace drivers/mempool/octeontx2/ with drivers/mempool/cnxk/
> - Replace drivers/net/octeontx2/ with drivers/net/cnxk/
> - Replace drivers/event/octeontx2/ with drivers/event/cnxk/
> - Replace drivers/crypto/octeontx2/ with drivers/crypto/cnxk/
> - Rename drivers/regex/octeontx2/ as drivers/regex/cn9k/
> - Rename config/arm/arm64_octeontx2_linux_gcc as
> config/arm/arm64_cn9k_linux_gcc
>
> Last two actions are to align naming convention as cnxk scheme.
>
> Signed-off-by: Jerin Jacob<jerinj@marvell.com>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2021-11-09 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 15:51 jerinj
2021-11-09 15:58 ` Ferruh Yigit [this message]
2021-11-12 11:24 ` [EXT] " Akhil Goyal
2021-11-24 15:08 ` Thomas Monjalon
2021-11-24 15:48 ` Thomas Monjalon
2021-11-24 15:20 ` David Marchand
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=c8c32cb1-a06d-60c4-6bb3-de42217e381f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=lironh@marvell.com \
--cc=mdr@ashroe.eu \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=thomas@monjalon.net \
/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).