DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ray Kinsella <mdr@ashroe.eu>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [PATCH 1/4] rte_log: take of some experimental tags
Date: Thu, 17 Feb 2022 07:57:34 -0500	[thread overview]
Message-ID: <875ypdfy69.fsf@mdr78.vserver.site> (raw)
In-Reply-To: <20220216193917.251657-2-stephen@networkplumber.org>


Stephen Hemminger <stephen@networkplumber.org> writes:

> The RTE_LOG_REGISTER is not experimental, and the experimental
> tag was never enforced on these.
>
> Make rte_log_can_log a fully supported function.
> It was introduced nearly 2yrs ago.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  lib/eal/include/rte_log.h | 10 ----------
>  lib/eal/version.map       |  2 +-
>  2 files changed, 1 insertion(+), 11 deletions(-)

Acked-by: Ray Kinsella <mdr@ashroe.eu>

-- 
Regards, Ray K

  reply	other threads:[~2022-02-17 12:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 19:39 [PATCH 0/4] eal: remove " Stephen Hemminger
2022-02-16 19:39 ` [PATCH 1/4] rte_log: take of " Stephen Hemminger
2022-02-17 12:57   ` Ray Kinsella [this message]
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=875ypdfy69.fsf@mdr78.vserver.site \
    --to=mdr@ashroe.eu \
    --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).