From: Jerin Jacob <jerinjacobk@gmail.com>
To: pbhagavatula@marvell.com
Cc: jerinj@marvell.com, Ray Kinsella <mdr@ashroe.eu>, dev@dpdk.org
Subject: Re: [PATCH 3/3] doc: remove deprecation notices for event vector
Date: Fri, 30 Sep 2022 15:46:36 +0530 [thread overview]
Message-ID: <CALBAE1PT7N4hbsB6Nnr7e2Y80o9Cak-EF-riVTfVs-g7NEDoew@mail.gmail.com> (raw)
In-Reply-To: <20220929095748.12563-3-pbhagavatula@marvell.com>
On Thu, Sep 29, 2022 at 3:30 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Deprecation notice targeted for v22.11 of event vector has been
> merged in the following commits, remove deprecation notices.
>
> Fixes: 7b12f13ce3ee ("eventdev: add element offset to event vector")
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Series-Acked-by: Jerin Jacob <jerinj@marvell.com>
Series applied to dpdk-next-eventdev/for-main. Thanks.
> ---
> doc/guides/rel_notes/deprecation.rst | 7 -------
> 1 file changed, 7 deletions(-)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index bb44b1f9ff..9679615f95 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -173,13 +173,6 @@ Deprecation Notices
> Event will be one of the configuration fields,
> together with additional vector parameters.
>
> -* eventdev: The structure ``rte_event_vector`` will be modified to include
> - ``elem_offset:12`` bits taken from ``rsvd:15``. The ``elem_offset`` defines
> - the offset into the vector array from which valid elements are present.
> - The difference between ``rte_event_vector::nb_elem`` and
> - ``rte_event_vector::elem_offset`` gives the number of valid elements left
> - to process from the ``rte_event_vector::elem_offset``.
> -
> * metrics: The function ``rte_metrics_init`` will have a non-void return
> in order to notify errors instead of calling ``rte_exit``.
>
> --
> 2.25.1
>
prev parent reply other threads:[~2022-09-30 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 9:57 [PATCH 1/3] eventdev: add rte prefix to function declaration pbhagavatula
2022-09-29 9:57 ` [PATCH 2/3] eventdev: replace *u64s with u64s in event vector pbhagavatula
2022-09-29 9:57 ` [PATCH 3/3] doc: remove deprecation notices for " pbhagavatula
2022-09-30 10:16 ` 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=CALBAE1PT7N4hbsB6Nnr7e2Y80o9Cak-EF-riVTfVs-g7NEDoew@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mdr@ashroe.eu \
--cc=pbhagavatula@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).