From: David Marchand <david.marchand@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Kevin Traynor <ktraynor@redhat.com>,
Joyce Kong <Joyce.Kong@arm.com>, "dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"techboard@dpdk.org" <techboard@dpdk.org>,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: Re: [PATCH] bitops: mark new symbols as stable
Date: Mon, 23 Oct 2023 16:08:59 +0200 [thread overview]
Message-ID: <CAJFAV8zRM-Cap7ZHY5GoXVphH6RnivPu7=HYWa3ETGhzim8sSA@mail.gmail.com> (raw)
In-Reply-To: <918876a3-3fb0-a2af-f466-d24a58e117af@redhat.com>
On Mon, Oct 23, 2023 at 10:47 AM Kevin Traynor <ktraynor@redhat.com> wrote:
> >> Calling an experimental symbol from an inline helper triggers a warning when
> >> such code is not compiled with experimental API.
> >> This can be seen when rte_bitops.h gets (indirectly) included in OVS builds.
> >>
> >> On the other hand, rte_clz32, rte_clz64, rte_ctz32, rte_ctz64, rte_popcount32,
> >> rte_popcount64 are inline helpers for abstracting common bit counting
> >> functions. This part of the API is unlikely to change.
> >>
> >> Mark those symbols as stable.
> >>
> >> Fixes: 18898c4d06f9 ("eal: use abstracted bit count functions")
> >>
> >> Signed-off-by: David Marchand <david.marchand@redhat.com>
> > Reviewed-by: Joyce Kong <joyce.kong@arm.com>
> Acked-by: Kevin Traynor <ktraynor@redhat.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2023-10-23 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 9:11 David Marchand
2023-10-23 7:09 ` Joyce Kong
2023-10-23 8:47 ` Kevin Traynor
2023-10-23 14:08 ` David Marchand [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='CAJFAV8zRM-Cap7ZHY5GoXVphH6RnivPu7=HYWa3ETGhzim8sSA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=Joyce.Kong@arm.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=roretzla@linux.microsoft.com \
--cc=techboard@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).