From: Stephen Hemminger <stephen@networkplumber.org>
To: Joyce Kong <joyce.kong@arm.com>
Cc: thomas@monjalon.net, honnappa.nagarahalli@arm.com,
phil.yang@arm.com, ruifeng.wang@arm.com, dev@dpdk.org,
nd@arm.com
Subject: Re: [dpdk-dev] [PATCH 4/4] eal/pause: remove experimental tag from wait until equal
Date: Wed, 7 Jul 2021 07:42:24 -0700 [thread overview]
Message-ID: <20210707074224.6f086719@hermes.local> (raw)
In-Reply-To: <20200911054534.55378-5-joyce.kong@arm.com>
On Fri, 11 Sep 2020 13:45:34 +0800
Joyce Kong <joyce.kong@arm.com> wrote:
> rte_wait_until_equal_xx APIs were introduced in 19.11 release
> and there were no changes in the public APIs since then, it
> should be mature enough to remove the experimental tag.
>
> Signed-off-by: Joyce Kong <joyce.kong@arm.com>
> Reviewed-by: Phil Yang <phil.yang@arm.com>
> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2021-07-07 14:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 5:45 [dpdk-dev] [PATCH 0/4] remove experimental tags from APIs Joyce Kong
2020-09-11 5:45 ` [dpdk-dev] [PATCH 1/4] eal/ticketlock: remove experimental tag Joyce Kong
2020-09-11 5:45 ` [dpdk-dev] [PATCH 2/4] eal/mcslock: " Joyce Kong
2020-09-11 5:45 ` [dpdk-dev] [PATCH 3/4] rcu: remove experimental tag from QSBR mechanism Joyce Kong
2020-10-05 8:54 ` Kinsella, Ray
2020-09-11 5:45 ` [dpdk-dev] [PATCH 4/4] eal/pause: remove experimental tag from wait until equal Joyce Kong
2021-07-07 14:42 ` Stephen Hemminger [this message]
2020-09-16 17:09 ` [dpdk-dev] [PATCH 0/4] remove experimental tags from APIs David Marchand
2020-09-25 14:12 ` David Marchand
2020-09-25 14:14 ` Ananyev, Konstantin
2020-10-05 19:39 ` David Christensen
2020-10-05 8:39 ` Kinsella, Ray
2020-10-05 12:18 ` David Marchand
2020-10-06 8:30 ` David Marchand
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=20210707074224.6f086719@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=joyce.kong@arm.com \
--cc=nd@arm.com \
--cc=phil.yang@arm.com \
--cc=ruifeng.wang@arm.com \
--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).