From: Jerin Jacob <jerinjacobk@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
Ray Kinsella <mdr@ashroe.eu>,
Jay Jayatheerthan <jay.jayatheerthan@intel.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
Harman Kalra <hkalra@marvell.com>,
Abhinandan Gujjar <abhinandan.gujjar@intel.com>,
Shijith Thotton <sthotton@marvell.com>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] doc: remove deprecation notices for eventdev
Date: Thu, 4 Nov 2021 19:24:09 +0530 [thread overview]
Message-ID: <CALBAE1NM951wm65yao7EGmetvq-WTY1hhBmEjdAresdwYd4YcQ@mail.gmail.com> (raw)
In-Reply-To: <CALBAE1OKvC8zWmaR47FRR_oj=vPrOF4JN5+Cn8bkZuaUe+6r4g@mail.gmail.com>
On Tue, Nov 2, 2021 at 9:59 PM Jerin Jacob <jerinjacobk@gmail.com> wrote:
>
> On Tue, Nov 2, 2021 at 9:31 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > 02/11/2021 16:49, jerinj@marvell.com:
> > > From: Jerin Jacob <jerinj@marvell.com>
> > >
> > > All deprecation notice targeted for v21.11 of eventdev has been
> > > committed in the following commits, remove deprecation notices.
> > >
> > > Fixes: 3c838062b91 ("eventdev: introduce event vector Rx capability")
> > > Fixes: 929ebdd5430 ("eventdev/eth_rx: simplify event vector config")
> > > Fixes: 295c053f90f ("eventdev: hide event device related structures")
> > > Fixes: dd451ad1520 ("doc: remove event crypto metadata deprecation note")
>
> Reported-by: David Marchand <david.marchand@redhat.com>
Applied to dpdk-next-net-eventdev/for-main. Thanks
prev parent reply other threads:[~2021-11-04 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 15:49 jerinj
2021-11-02 16:01 ` Thomas Monjalon
2021-11-02 16:29 ` Jerin Jacob
2021-11-02 19:58 ` David Marchand
2021-11-04 13:54 ` Jerin Jacob [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=CALBAE1NM951wm65yao7EGmetvq-WTY1hhBmEjdAresdwYd4YcQ@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=abhinandan.gujjar@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinj@marvell.com \
--cc=mdr@ashroe.eu \
--cc=pbhagavatula@marvell.com \
--cc=sthotton@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).