From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: "Kinsella, Ray" <mdr@ashroe.eu>,
Thomas Monjalon <thomas@monjalon.net>,
dev@dpdk.org
Cc: matan@nvidia.com, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] ethdev: promote device removal check function as stable
Date: Thu, 28 Oct 2021 11:56:58 +0300 [thread overview]
Message-ID: <351668ab-92d7-9726-3168-c5aefbb71492@oktetlabs.ru> (raw)
In-Reply-To: <ba8e94b2-661d-4d34-6c09-903aa2f74d6b@ashroe.eu>
On 10/28/21 11:38 AM, Kinsella, Ray wrote:
>
>
> On 28/10/2021 09:35, Thomas Monjalon wrote:
>> The function rte_eth_dev_is_removed() was introduced in DPDK 18.02,
>> and is integrated in error checks of ethdev library.
>>
>> It is promoted as stable ABI.
>>
>> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>> ---
>> lib/ethdev/rte_ethdev.h | 4 ----
>> lib/ethdev/version.map | 2 +-
>> 2 files changed, 1 insertion(+), 5 deletions(-)
>>
> Acked-by: Ray Kinsella <mdr@ashroe.eu>
Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
next prev parent reply other threads:[~2021-10-28 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 8:35 Thomas Monjalon
2021-10-28 8:38 ` Kinsella, Ray
2021-10-28 8:56 ` Andrew Rybchenko [this message]
2021-11-04 10:45 ` 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=351668ab-92d7-9726-3168-c5aefbb71492@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=matan@nvidia.com \
--cc=mdr@ashroe.eu \
--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).