All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Kevin Traynor <ktraynor@redhat.com>,
	Reshma Pattan <reshma.pattan@intel.com>,
	Maryam Tahhan <maryam.tahhan@intel.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Anatoly Burakov <anatoly.burakov@intel.com>,
	John McNamara <john.mcnamara@intel.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Harry van Haaren <harry.van.haaren@intel.com>,
	Xiaoyun Li <xiaoyun.li@intel.com>,
	david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH] eal: promote some experimental functions as stable
Date: Sun, 21 Apr 2019 19:12:41 +0200	[thread overview]
Message-ID: <1705204.UzZM88U6YT@xps> (raw)
In-Reply-To: <4243200a-66d2-7ee0-49b6-acc75bf9a805@redhat.com>

18/04/2019 12:02, Kevin Traynor:
> On 18/04/2019 01:30, Thomas Monjalon wrote:
> > The function rte_eal_cleanup() was introduced more than one year ago,
> > in DPDK 18.02. It is no longer experimental, allowing
> > pdump, proc-info and hotplug_mp apps to not need any experimental API.
> > 
> > The function rte_ctrl_thread_create() was introduced one year ago
> > in DPDK 18.05. It is no longer experimental, allowing
> > KNI PMD and TEP example to not need any experimental API.
> > 
> > The functions rte_socket_count() and rte_socket_id_by_idx() were
> > introduced one year ago in DPDK 18.05. They are no longer experimental.
> > 
> > The function rte_dev_is_probed() was introduced half a year ago
> > in DPDK 18.11. It is no longer experimental.
> > 
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> 
> Acked-by: Kevin Traynor <ktraynor@redhat.com>

Applied




      reply	other threads:[~2019-04-21 17:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18  0:30 [dpdk-dev] [PATCH] eal: promote some experimental functions as stable Thomas Monjalon
2019-04-18  9:23 ` [dpdk-dev] [EXT] " Hemant Agrawal
2019-04-18 10:02 ` [dpdk-dev] " Kevin Traynor
2019-04-21 17:12   ` Thomas Monjalon [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=1705204.UzZM88U6YT@xps \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=maryam.tahhan@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=reshma.pattan@intel.com \
    --cc=xiaoyun.li@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.