From: Thomas Monjalon <thomas@monjalon.net>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: jerinj@marvell.com, Ray Kinsella <mdr@ashroe.eu>, dev@dpdk.org
Subject: Re: [PATCH] doc: announce change in event vector structure
Date: Sun, 17 Jul 2022 14:42:21 +0200 [thread overview]
Message-ID: <3171904.oiGErgHkdL@thomas> (raw)
In-Reply-To: <20220624090951.4833-1-pbhagavatula@marvell.com>
24/06/2022 11:09, pbhagavatula@marvell.com:
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> The field `*u64s` in the structure `rte_event_vector` will
> be replaced with `u64s`.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---
> +* eventdev: The element ``*u64s`` in the structure ``rte_event_vector`` is
> + deprecated and will be replaced with ``u64s`` in DPDK 22.11.
Acked-by: Jerin Jacob <jerinj@marvell.com>
Acked-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
Acked-by: Jay Jayatheerthan <jay.jayetheerthan@intel.com>
Applied, thanks.
prev parent reply other threads:[~2022-07-17 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 9:09 pbhagavatula
2022-07-11 14:51 ` Jerin Jacob
2022-07-12 18:15 ` [EXT] " Pavan Nikhilesh Bhagavatula
2022-07-13 7:03 ` Gujjar, Abhinandan S
2022-07-13 10:17 ` Jayatheerthan, Jay
2022-07-17 12:42 ` 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=3171904.oiGErgHkdL@thomas \
--to=thomas@monjalon.net \
--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).