DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 3/3] rwlock: make trylock operations no longer experimental
Date: Mon, 17 Oct 2022 18:57:20 -0700	[thread overview]
Message-ID: <20221018015720.411702-4-stephen@networkplumber.org> (raw)
In-Reply-To: <20221018015720.411702-1-stephen@networkplumber.org>

These have been in for since 19.02, time to take off the
experimental tag.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 lib/eal/include/generic/rte_rwlock.h | 12 ++----------
 1 file changed, 2 insertions(+), 10 deletions(-)

diff --git a/lib/eal/include/generic/rte_rwlock.h b/lib/eal/include/generic/rte_rwlock.h
index 90f77dfe23b0..233d4262bede 100644
--- a/lib/eal/include/generic/rte_rwlock.h
+++ b/lib/eal/include/generic/rte_rwlock.h
@@ -108,10 +108,7 @@ rte_rwlock_read_lock(rte_rwlock_t *rwl)
 }
 
 /**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
- * try to take a read lock.
+ * Try to take a read lock.
  *
  * @param rwl
  *   A pointer to a rwlock structure.
@@ -120,7 +117,6 @@ rte_rwlock_read_lock(rte_rwlock_t *rwl)
  *   - -EBUSY if lock could not be acquired for reading because a
  *     writer holds the lock
  */
-__rte_experimental
 static inline int
 rte_rwlock_read_trylock(rte_rwlock_t *rwl)
 {
@@ -159,10 +155,7 @@ rte_rwlock_read_unlock(rte_rwlock_t *rwl)
 }
 
 /**
- * @warning
- * @b EXPERIMENTAL: this API may change without prior notice.
- *
- * try to take a write lock.
+ * Try to take a write lock.
  *
  * @param rwl
  *   A pointer to a rwlock structure.
@@ -171,7 +164,6 @@ rte_rwlock_read_unlock(rte_rwlock_t *rwl)
  *   - -EBUSY if lock could not be acquired for writing because
  *     it was already locked for reading or writing
  */
-__rte_experimental
 static inline int
 rte_rwlock_write_trylock(rte_rwlock_t *rwl)
 {
-- 
2.35.1


  parent reply	other threads:[~2022-10-18  1:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  1:57 [PATCH 0/3] remove more experimental tags Stephen Hemminger
2022-10-18  1:57 ` [PATCH 1/3] eal: remove experimental from rte_epoll_wait_interruptible Stephen Hemminger
2022-10-18  1:57 ` [PATCH 2/3] eal: make rte_log_list_types not experimental Stephen Hemminger
2022-10-18  1:57 ` Stephen Hemminger [this message]
2022-10-18 14:15 ` [PATCH 0/3] remove more experimental tags David Marchand
2022-10-27 11:16 ` 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=20221018015720.411702-4-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    /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).