From: Thomas Monjalon <thomas@monjalon.net>
To: Alok Prasad <palok@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>,
Devendra Singh Rawat <dsinghrawat@marvell.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
techboard@dpdk.org
Subject: Re: [PATCH] doc: deprecation notice to remove net/bnx2x driver
Date: Fri, 31 Mar 2023 15:34:57 +0200 [thread overview]
Message-ID: <5431020.TLkxdtWsSY@thomas> (raw)
In-Reply-To: <cba0b411-07e7-cc53-a21a-e3caf8563f5f@amd.com>
> >> From: Jerin Jacob <jerinj@marvell.com>
> >>
> >> Starting from DPDK 23.07, the Marvell QLogic bnx2x driver
> >> will be removed. This decision has been made to alleviate the burden of
> >> maintaining a discontinued product.
> >>
> >> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> >
> > Acked-by: Alok Prasad <palok@marvell.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
I agree we should remove this driver.
But I'm afraid the notice may be a bit short in time.
Could we proceed as for the LiquidIO driver?
The bnx2x driver could be declared unmaintained in 23.07,
and then removed in 23.11.
In any case it is good to have a notice as early as possible,
even if the plan is slightly postponed.
Please let's discuss the execution plan during a Technical Board meeting.
Applied as-is for 23.03 release, thanks.
prev parent reply other threads:[~2023-03-31 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 12:30 [dpdk-dev] " jerinj
2023-03-17 18:02 ` Alok Prasad
2023-03-21 10:40 ` Ferruh Yigit
2023-03-30 12:47 ` Jerin Jacob
2023-03-31 13:34 ` Thomas Monjalon [this message]
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=5431020.TLkxdtWsSY@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dsinghrawat@marvell.com \
--cc=ferruh.yigit@amd.com \
--cc=jerinj@marvell.com \
--cc=palok@marvell.com \
--cc=techboard@dpdk.org \
/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).