From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>,
Gage Eads <gage.eads@intel.com>
Cc: Jerin Jacob <jerinj@marvell.com>, Ray Kinsella <mdr@ashroe.eu>,
dpdk-dev <dev@dpdk.org>
Subject: Re: [PATCH] doc: announce name change of stop flush callback
Date: Mon, 11 Jul 2022 20:20:38 +0530 [thread overview]
Message-ID: <CALBAE1PTBwNyFjcDGb=1iSQjt0zOnD3stBObtKK47mDjMS94=w@mail.gmail.com> (raw)
In-Reply-To: <20220624090828.2020-1-pbhagavatula@marvell.com>
On Fri, Jun 24, 2022 at 2:40 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Stop flush callback is missing `rte_` prefix and might conflict with
> application declarations.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
+ @Gage Eads
> ---
> doc/guides/rel_notes/deprecation.rst | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 4e5b23c53d..a3c4f4ac09 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -125,3 +125,6 @@ Deprecation Notices
> applications should be updated to use the ``dmadev`` library instead,
> with the underlying HW-functionality being provided by the ``ioat`` or
> ``idxd`` dma drivers
> +
> +* eventdev: The function pointer declaration ``eventdev_stop_flush_t`` will be
> + renamed to ``rte_eventdev_stop_flush_t`` in DPDK 22.11.
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-07-11 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 9:08 pbhagavatula
2022-07-11 14:50 ` Jerin Jacob [this message]
2022-07-12 18:12 ` [EXT] " Pavan Nikhilesh Bhagavatula
2022-07-13 9:11 ` Mattias Rönnblom
2022-07-14 11:21 ` Van Haaren, Harry
2022-07-17 12:25 ` 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='CALBAE1PTBwNyFjcDGb=1iSQjt0zOnD3stBObtKK47mDjMS94=w@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--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).