From: "Kinsella, Ray" <mdr@ashroe.eu>
To: David Marchand <david.marchand@redhat.com>, dev@dpdk.org
Cc: thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH] doc: announce internal hotplug structure removal
Date: Thu, 6 Aug 2020 14:59:12 +0100 [thread overview]
Message-ID: <67f0fa13-89b3-750b-8840-e90343e76b6a@ashroe.eu> (raw)
In-Reply-To: <20200804140717.8659-1-david.marchand@redhat.com>
On 04/08/2020 15:07, David Marchand wrote:
> rte_dev_event has never been used outside of the EAL.
> No point in exposing it.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> 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 24808c002c..9f73297173 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -27,6 +27,9 @@ Deprecation Notices
> remove it from the externally visible ABI and allow it to be updated in the
> future.
>
> +* eal: The ``rte_dev_event`` structure will be made private to the EAL as no
> + public API makes use of it.
> +
> * rte_atomicNN_xxx: These APIs do not take memory order parameter. This does
> not allow for writing optimized code for all the CPU architectures supported
> in DPDK. DPDK will adopt C11 atomic operations semantics and provide wrappers
>
Acked-by: Ray Kinsella <mdr@ashroe.eu>
prev parent reply other threads:[~2020-08-06 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 14:07 David Marchand
2020-08-04 14:29 ` Bruce Richardson
2020-08-06 16:30 ` Thomas Monjalon
2020-08-06 12:07 ` Andrew Rybchenko
2020-08-06 13:59 ` Kinsella, Ray [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=67f0fa13-89b3-750b-8840-e90343e76b6a@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--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).