From: Bernard Iremonger <bernard.iremonger@intel.com>
To: dev@dpdk.org, john.mcnamara@intel.com
Cc: Bernard Iremonger <bernard.iremonger@intel.com>
Subject: [dpdk-dev] [PATCH v1] doc: announce API change for ethdev function
Date: Tue, 18 Oct 2016 14:38:08 +0100 [thread overview]
Message-ID: <1476797888-29698-2-git-send-email-bernard.iremonger@intel.com> (raw)
In-Reply-To: <1476797888-29698-1-git-send-email-bernard.iremonger@intel.com>
The _rte_eth_dev_call_process function will change to return "int"
and a fourth parameter "void* ret_param" will be added. This change
targets release 17.02.
Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
---
doc/guides/rel_notes/deprecation.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index d5c1490..1d274d8 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -49,3 +49,7 @@ Deprecation Notices
* mempool: The functions for single/multi producer/consumer are deprecated
and will be removed in 17.02.
It is replaced by ``rte_mempool_generic_get/put`` functions.
+
+* librte_ether: an API change is planned for 17.02 for the function
+ ``_rte_eth_dev_callback_process``. In 17.02 the function will return an ``int``
+ instead of ``void`` and a fourth parameter ``void *ret_param`` will be added.
--
2.10.1
next prev parent reply other threads:[~2016-10-18 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 13:38 [dpdk-dev] [PATCH v1] doc: announce API and ABI change for librte_ether Bernard Iremonger
2016-10-18 13:38 ` Bernard Iremonger [this message]
2016-11-04 13:39 ` [dpdk-dev] [PATCH v1] doc: announce API change for ethdev function Mcnamara, John
2016-11-13 9:16 ` Thomas Monjalon
2016-11-04 13:39 ` [dpdk-dev] [PATCH v1] doc: announce API and ABI change for librte_ether Mcnamara, John
2016-11-10 10:36 ` Ferruh Yigit
2016-11-13 13:46 ` Thomas Monjalon
2016-11-10 10:26 ` Pattan, Reshma
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=1476797888-29698-2-git-send-email-bernard.iremonger@intel.com \
--to=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).