From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/3] remove more experimental tags
Date: Thu, 27 Oct 2022 13:16:24 +0200 [thread overview]
Message-ID: <CAJFAV8xjiukeR9h=8+3xVScZUtuch8ahmJeVvV5oFkw0EYyvEg@mail.gmail.com> (raw)
In-Reply-To: <20221018015720.411702-1-stephen@networkplumber.org>
On Tue, Oct 18, 2022 at 3:58 AM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> Remove some of the older experimental tags for 22.11
>
> Stephen Hemminger (3):
> eal: remove experimental from rte_epoll_wait_interruptible
> eal: make rte_log_list_types not experimental
> rwlock: make trylock operations no longer experimental
>
> lib/eal/include/generic/rte_rwlock.h | 12 ++----------
> lib/eal/include/rte_epoll.h | 1 -
> lib/eal/include/rte_log.h | 4 ----
> lib/eal/version.map | 4 ++--
> 4 files changed, 4 insertions(+), 17 deletions(-)
Series applied.
I added to my todolist that we need a cleanup for unneeded inclusion
of rte_compat.h (the headers touched in this series are not the only
one concerned).
--
David Marchand
prev parent reply other threads:[~2022-10-27 11:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 1:57 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 ` [PATCH 3/3] rwlock: make trylock operations no longer experimental Stephen Hemminger
2022-10-18 14:15 ` [PATCH 0/3] remove more experimental tags David Marchand
2022-10-27 11:16 ` 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='CAJFAV8xjiukeR9h=8+3xVScZUtuch8ahmJeVvV5oFkw0EYyvEg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).