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 0/4]  eal: remove some experimental tags
Date: Wed, 16 Feb 2022 11:39:13 -0800	[thread overview]
Message-ID: <20220216193917.251657-1-stephen@networkplumber.org> (raw)

These are all functions that have been in DPDK for two
years or more and should no longer be experimental.

Stephen Hemminger (4):
  rte_log: take of some experimental tags
  lcore: change rte_lcore_to_cpu_id and rte_lcore_cpuset as not
    experimental
  eal: make some intr functions not experimental
  eal: mark rte_delay_us_sleep as not experimental

 lib/eal/include/generic/rte_cycles.h |  4 +---
 lib/eal/include/rte_interrupts.h     | 12 +-----------
 lib/eal/include/rte_lcore.h          |  9 +--------
 lib/eal/include/rte_log.h            | 10 ----------
 lib/eal/version.map                  | 18 +++++++-----------
 5 files changed, 10 insertions(+), 43 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-02-16 19:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 19:39 Stephen Hemminger [this message]
2022-02-16 19:39 ` [PATCH 1/4] rte_log: take of " Stephen Hemminger
2022-02-17 12:57   ` Ray Kinsella
2022-02-16 19:39 ` [PATCH 2/4] lcore: change rte_lcore_to_cpu_id and rte_lcore_cpuset as not experimental Stephen Hemminger
2022-02-17 12:55   ` Ray Kinsella
2022-02-16 19:39 ` [PATCH 3/4] eal: make some intr functions " Stephen Hemminger
2022-02-17 12:56   ` Ray Kinsella
2022-02-16 19:39 ` [PATCH 4/4] eal: mark rte_delay_us_sleep as " Stephen Hemminger
2022-02-17 12:56   ` Ray Kinsella
2022-06-26 15:34 ` [PATCH 0/4] eal: remove some experimental tags 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=20220216193917.251657-1-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).