From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, grive@u256.net, david.marchand@redhat.com,
wenzhuo.lu@intel.com, beilei.xing@intel.com,
bernard.iremonger@intel.com,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] doc: announce rte_dev_probe() API change
Date: Fri, 31 Jul 2020 09:20:11 +0200 [thread overview]
Message-ID: <8b957e82-2f87-7d02-4ea0-56f7baa1eab8@redhat.com> (raw)
In-Reply-To: <20200625080430.1392037-2-maxime.coquelin@redhat.com>
Hi Thomas, Davis,
On 6/25/20 10:04 AM, Maxime Coquelin wrote:
> 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 d1034f60fd..8661a673b5 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -130,3 +130,8 @@ Deprecation Notices
> Python 2 support will be completely removed in 20.11.
> In 20.08, explicit deprecation warnings will be displayed when running
> scripts with Python 2.
> +
> +* eal: Change ``rte_dev_probe`` API in DPDK v20.11 to return a pointer on the
> + probed rte_device or NULL instead of 0 or an error code. This change will
> + allow applications avoid iterating on devices after a probe to get access to
> + the new rte_device.
>
Any chance this patch goes into -rc4?
Patch 2 is for v20.11, but we would need the deprecation notice to be in
v20.08.
Thanks,
Maxime
next prev parent reply other threads:[~2020-07-31 7:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 8:04 [dpdk-dev] [PATCH v2 0/2] " Maxime Coquelin
2020-06-25 8:04 ` [dpdk-dev] [PATCH v2 1/2] doc: announce " Maxime Coquelin
2020-07-31 7:20 ` Maxime Coquelin [this message]
2020-07-31 9:26 ` Bruce Richardson
2020-07-31 9:44 ` Gaëtan Rivet
2020-07-31 9:47 ` Maxime Coquelin
2020-08-04 8:12 ` David Marchand
2020-08-04 8:53 ` Jerin Jacob
2020-06-25 8:04 ` [dpdk-dev] [PATCH v2 (v20.11) 2/2] eal: improve device probing API Maxime Coquelin
2020-06-29 9:57 ` Gaëtan Rivet
2020-08-05 23:33 ` Thomas Monjalon
2020-08-06 10:29 ` Maxime Coquelin
2020-08-06 11:43 ` 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=8b957e82-2f87-7d02-4ea0-56f7baa1eab8@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=thomas@monjalon.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).