From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob <jerinj@marvell.com>
Cc: 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>,
jerinj@marvell.com, david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH] doc: remove deprecation notices for eventdev
Date: Tue, 02 Nov 2021 17:01:30 +0100 [thread overview]
Message-ID: <15290575.q2TZQeXj09@thomas> (raw)
In-Reply-To: <20211102154956.1443591-1-jerinj@marvell.com>
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")
That's not an easy job, but we should really try to make such change
in the related commits, like any other doc or test updates.
I keep forgetting such things as well.
next prev parent reply other threads:[~2021-11-02 16:01 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 [this message]
2021-11-02 16:29 ` Jerin Jacob
2021-11-02 19:58 ` David Marchand
2021-11-04 13:54 ` Jerin Jacob
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=15290575.q2TZQeXj09@thomas \
--to=thomas@monjalon.net \
--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 \
/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).