From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, david.marchand@redhat.com, wenzhuo.lu@intel.com,
beilei.xing@intel.com, bernard.iremonger@intel.com,
grive@u256.net
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-dev] [PATCH 1/2] doc: announce rte_dev_probe() API change
Date: Mon, 8 Jun 2020 17:53:29 +0200 [thread overview]
Message-ID: <20200608155330.163874-2-maxime.coquelin@redhat.com> (raw)
In-Reply-To: <20200608155330.163874-1-maxime.coquelin@redhat.com>
In order to simplify the use of rte_dev_probe() and
rte_dev_remove() by applications, rte_dev_probe() will
return a reference on the rte_device stating DPDK v20.11.
Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
---
doc/guides/rel_notes/deprecation.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 0bee924255..47151eac0b 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -138,3 +138,8 @@ Deprecation Notices
driver probe scheme. The legacy virtio support will be available through
the existing VFIO/UIO based kernel driver scheme.
More details at https://patches.dpdk.org/patch/69351/
+
+* eal: Change ``rte_dev_probe`` API to return a pointer on the probed
+ rte_device or NULL instead of 0 or an error code in DPDK v20.11. This
+ change will help calling application in avoiding to iterate the devices
+ list when willing to call rte_dev_remove() later.
--
2.26.2
next prev parent reply other threads:[~2020-06-08 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 15:53 [dpdk-dev] [PATCH 0/2] " Maxime Coquelin
2020-06-08 15:53 ` Maxime Coquelin [this message]
2020-06-11 8:08 ` [dpdk-dev] [PATCH 1/2] doc: announce " Gaëtan Rivet
2020-06-25 7:50 ` Maxime Coquelin
2020-06-08 15:53 ` [dpdk-dev] [PATCH v20.11 2/2] eal: improve device probing API Maxime Coquelin
2020-06-10 12:06 ` Gaëtan Rivet
2020-06-10 17:08 ` Maxime Coquelin
2020-06-10 18:13 ` Gaëtan Rivet
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=20200608155330.163874-2-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=grive@u256.net \
--cc=wenzhuo.lu@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 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).