From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Kollanukkaran <jerinj@marvell.com>
Cc: dpdk-dev <dev@dpdk.org>, Prasun Kapoor <pkapoor@marvell.com>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
"Andrzej Ostruszka [C]" <aostruszka@marvell.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Satheesh Paul <psatheesh@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Narayana Prasad Raju Athreya <pathreya@marvell.com>,
Dovrat Zifroni <dovrat@marvell.com>,
Igor Russkikh <irusskikh@marvell.com>,
Ameen Rahman <arahman@marvell.com>,
Rasesh Mody <rmody@marvell.com>,
Nagadheeraj Rottela <rnagadheeraj@marvell.com>,
Srikanth Jampala <jsrikanth@marvell.com>,
orika@mellanox.com
Subject: Re: [dpdk-dev] Marvell DPDK v20.08 Roadmap
Date: Tue, 02 Jun 2020 18:46:31 +0200 [thread overview]
Message-ID: <12832784.v2d1Wfp5JU@thomas> (raw)
In-Reply-To: <BYAPR18MB24249BC0D3EA17076D6CFB71C88F0@BYAPR18MB2424.namprd18.prod.outlook.com>
29/05/2020 14:50, Jerin Kollanukkaran:
> Regexdev:
> ~~~~~~~~~
> 11) Review regexdev: introduce regexdev subsystem
If I remember well, you were targetting DPDK 20.08
to introduce a new regex PMD.
I am surprised this roadmap mentions only reviewing the API.
next prev parent reply other threads:[~2020-06-02 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 12:50 Jerin Kollanukkaran
2020-06-02 16:46 ` Thomas Monjalon [this message]
2020-06-02 17:36 ` Jerin Jacob
2020-06-02 18:34 ` Ori Kam
2020-06-03 3:10 ` Jerin Jacob
2020-06-02 21:58 ` Thomas Monjalon
2020-06-03 3:14 ` Jerin Jacob
2023-07-31 13:06 ` Thomas Monjalon
2023-07-31 13:08 ` Jerin Jacob
2023-07-31 13:53 ` Thomas Monjalon
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=12832784.v2d1Wfp5JU@thomas \
--to=thomas@monjalon.net \
--cc=anoobj@marvell.com \
--cc=aostruszka@marvell.com \
--cc=arahman@marvell.com \
--cc=dev@dpdk.org \
--cc=dovrat@marvell.com \
--cc=irusskikh@marvell.com \
--cc=jerinj@marvell.com \
--cc=jsrikanth@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=orika@mellanox.com \
--cc=pathreya@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=pkapoor@marvell.com \
--cc=psatheesh@marvell.com \
--cc=rmody@marvell.com \
--cc=rnagadheeraj@marvell.com \
--cc=skori@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).