From: Radha Mohan <mohun106@gmail.com>
To: Radha Mohan Chintakuntla <radhac@marvell.com>
Cc: Veerasenareddy Burru <vburru@marvell.com>,
Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>,
Satananda Burla <sburla@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v4 2/2] drivers/raw: remove octeontx2-ep driver
Date: Mon, 23 Aug 2021 17:49:32 +0530 [thread overview]
Message-ID: <CAC8NTUXHdszN8LVm6NkYfb+EPQRi0_8pMqnG61yfB610D_PzWQ@mail.gmail.com> (raw)
In-Reply-To: <20210819075920.103301-1-radhac@marvell.com>
On Thu, Aug 19, 2021 at 1:29 PM Radha Mohan Chintakuntla
<radhac@marvell.com> wrote:
>
> Removing the rawdev based octeontx2-ep driver as the dependent
> common/octeontx2 will soon be going away. Moreover this driver is no
> longer required as the net/octeontx_ep driver is sufficient.
>
> Signed-off-by: Radha Mohan Chintakuntla <radhac@marvell.com>
> ---
> Changes from v3:
> Fixed patch application failure due to conflict on main branch.
>
> Changes from v2:
> Fixed DPDK CI reported issues for more documentation failure.
>
> Changes from v1:
> Fixed compilation issues in documentation
>
> MAINTAINERS | 6 -
> doc/guides/rawdevs/index.rst | 1 -
> doc/guides/rawdevs/octeontx2_ep.rst | 82 ---
> drivers/raw/meson.build | 1 -
> drivers/raw/octeontx2_ep/meson.build | 11 -
> drivers/raw/octeontx2_ep/otx2_ep_enqdeq.c | 846 ----------------------
> drivers/raw/octeontx2_ep/otx2_ep_enqdeq.h | 52 --
> drivers/raw/octeontx2_ep/otx2_ep_rawdev.c | 362 ---------
> drivers/raw/octeontx2_ep/otx2_ep_rawdev.h | 499 -------------
> drivers/raw/octeontx2_ep/otx2_ep_test.c | 172 -----
> drivers/raw/octeontx2_ep/otx2_ep_vf.c | 475 ------------
> drivers/raw/octeontx2_ep/otx2_ep_vf.h | 10 -
> drivers/raw/octeontx2_ep/version.map | 3 -
> 13 files changed, 2520 deletions(-)
> delete mode 100644 doc/guides/rawdevs/octeontx2_ep.rst
> delete mode 100644 drivers/raw/octeontx2_ep/meson.build
> delete mode 100644 drivers/raw/octeontx2_ep/otx2_ep_enqdeq.c
> delete mode 100644 drivers/raw/octeontx2_ep/otx2_ep_enqdeq.h
> delete mode 100644 drivers/raw/octeontx2_ep/otx2_ep_rawdev.c
> delete mode 100644 drivers/raw/octeontx2_ep/otx2_ep_rawdev.h
> delete mode 100644 drivers/raw/octeontx2_ep/otx2_ep_test.c
> delete mode 100644 drivers/raw/octeontx2_ep/otx2_ep_vf.c
> delete mode 100644 drivers/raw/octeontx2_ep/otx2_ep_vf.h
> delete mode 100644 drivers/raw/octeontx2_ep/version.map
>
<snip>
Hi Thomas,
I received this report that this patch failed to apply
http://mails.dpdk.org/archives/test-report/2021-August/211611.html
But I do not see the issue at my end.
$ git pull --rebase
remote: Counting objects: 17, done
remote: Finding sources: 100% (413/413)
remote: Total 413 (delta 315), reused 413 (delta 315)
Receiving objects: 100% (413/413), 148.64 KiB | 10.62 MiB/s, done.
Resolving deltas: 100% (315/315), completed with 125 local objects.
7a824dc305..df83c734ef dpdk-20.11-devel ->
origin/dpdk-20.11-devel
8b59a1248a..34b50fc2d3 dpdk-21.08-devel ->
origin/dpdk-21.08-devel
+ 9661f6ac43...fdab8f2e17 next-event ->
origin/next-event (forced update)
87d9bacc46..5803d86b87 next-net ->
origin/next-net
* [new branch] user/pbhagavatula/eventdev_abi ->
origin/user/pbhagavatula/eventdev_abi
056af3c7e5..55069aef6c user/skori/cnxk-ingress-policer-devel ->
origin/user/skori/cnxk-ingress-policer-devel
acd23283ff513c4f65290a7c92e9de25b912c0b1 (HEAD -> main) drivers/raw:
remove octeontx2-ep driver
463f4c93c4569fcb8a103d4e9231c4ba6c347b5e drivers/raw: remove
octeontx2-dma driver
fdab8f2e17493192d555cd88cf28b06269174326 (origin/next-event,
origin/main) version: 21.11-rc0
4ac3f3d76e9507a93bcf48d165ffd3a1faba08bb (origin/dpdk-21.08-release)
version: 21.08.0
293e836ea5e93dc923a114272798c5abbee7bae6 doc: announce changes in
IPsec xform structure
132293cb74a341ab05eae526b58c47efe2392b6c doc: announce change in IPsec
SA structure
eed159074e0e17dbd4971a0b9808f164c02acf5c doc: announce hiding crypto
session structures
regards,
Radha Mohan
> 2.24.1
>
next prev parent reply other threads:[~2021-08-23 12:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 12:37 [dpdk-dev] [PATCH v2 1/2] drivers/raw: remove octeontx2-dma driver Radha Mohan Chintakuntla
2021-08-13 7:00 ` [dpdk-dev] [PATCH v3 " Radha Mohan Chintakuntla
2021-08-19 7:57 ` [dpdk-dev] [PATCH v4 " Radha Mohan Chintakuntla
2021-08-20 3:38 ` Radha Mohan
2021-08-23 15:21 ` [dpdk-dev] [PATCH RESEND " Radha Mohan Chintakuntla
2021-08-23 15:21 ` [dpdk-dev] [PATCH RESEND v4 2/2] drivers/raw: remove octeontx2-ep driver Radha Mohan Chintakuntla
2021-08-23 16:27 ` Radha Mohan
2021-08-25 7:20 ` Thomas Monjalon
2021-08-26 10:50 ` [dpdk-dev] [PATCH v5 1/2] drivers/raw: remove octeontx2-dma driver Radha Mohan Chintakuntla
2021-08-26 10:50 ` [dpdk-dev] [PATCH v5 2/2] drivers/raw: remove octeontx2-ep driver Radha Mohan Chintakuntla
2021-08-26 11:10 ` Radha Mohan
2021-10-18 16:36 ` [dpdk-dev] [PATCH v5 1/2] drivers/raw: remove octeontx2-dma driver Thomas Monjalon
2021-08-13 7:01 ` [dpdk-dev] [PATCH v3 2/2] drivers/raw: remove octeontx2-ep driver Radha Mohan Chintakuntla
2021-08-19 7:59 ` [dpdk-dev] [PATCH v4 " Radha Mohan Chintakuntla
2021-08-23 12:19 ` Radha Mohan [this message]
2021-08-23 12:31 ` David Marchand
2021-08-23 12:41 ` Radha Mohan
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=CAC8NTUXHdszN8LVm6NkYfb+EPQRi0_8pMqnG61yfB610D_PzWQ@mail.gmail.com \
--to=mohun106@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=radhac@marvell.com \
--cc=sburla@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).