From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] ethdev: promote function for port count as stable
Date: Thu, 18 Apr 2019 15:34:57 +0300 [thread overview]
Message-ID: <1369aa06-4292-8b5e-470d-e067327ad202@solarflare.com> (raw)
Message-ID: <20190418123457.PzCIlK3oVVVg7dyj74ypx1nkxFQwemYZaOtEjZS5QrU@z> (raw)
In-Reply-To: <fd9d2a3c-16ce-8c16-5640-ff3e26299911@intel.com>
On 4/18/19 2:51 PM, Ferruh Yigit wrote:
> On 4/17/2019 11:59 PM, Thomas Monjalon wrote:
>> The function rte_eth_dev_count_total() was introduced one year ago
>> in the release 18.05. It can be declared non experimental in 19.05.
>>
>> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
next prev parent reply other threads:[~2019-04-18 12:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 22:59 [dpdk-dev] [PATCH 1/2] ethdev: avoid explicit check of valid port state Thomas Monjalon
2019-04-17 22:59 ` Thomas Monjalon
2019-04-17 22:59 ` [dpdk-dev] [PATCH 2/2] ethdev: promote function for port count as stable Thomas Monjalon
2019-04-17 22:59 ` Thomas Monjalon
2019-04-18 11:51 ` Ferruh Yigit
2019-04-18 11:51 ` Ferruh Yigit
2019-04-18 12:34 ` Andrew Rybchenko [this message]
2019-04-18 12:34 ` Andrew Rybchenko
2019-04-18 11:50 ` [dpdk-dev] [PATCH 1/2] ethdev: avoid explicit check of valid port state Ferruh Yigit
2019-04-18 11:50 ` Ferruh Yigit
2019-04-18 12:47 ` Thomas Monjalon
2019-04-18 12:47 ` Thomas Monjalon
2019-04-18 17:38 ` Thomas Monjalon
2019-04-18 17:38 ` Thomas Monjalon
2019-04-18 18:37 ` Ferruh Yigit
2019-04-18 18:37 ` Ferruh Yigit
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=1369aa06-4292-8b5e-470d-e067327ad202@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas@monjalon.net \
/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).