From: Bernard Iremonger <bernard.iremonger@intel.com>
To: dev@dpdk.org
Cc: john.mcnamara@intel.com, ferruh.yigit@intel.com,
Bernard Iremonger <bernard.iremonger@intel.com>
Subject: [PATCH] doc: postpone deprecation of functions in ethdev
Date: Tue, 18 Apr 2017 16:48:56 +0100 [thread overview]
Message-ID: <1492530536-2428-1-git-send-email-bernard.iremonger@intel.com> (raw)
The deprecation of the bypass functions in the ethdev has not been
done in 17.05. Let's postpone to 17.08.
Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
---
doc/guides/rel_notes/deprecation.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 00e379c00..5c44fa13e 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -40,7 +40,7 @@ Deprecation Notices
``_rte_eth_dev_callback_process``. In 17.08 the function will return an ``int``
instead of ``void`` and a fourth parameter ``void *ret_param`` will be added.
-* ethdev: for 17.05 it is planned to deprecate the following nine rte_eth_dev_*
+* ethdev: for 17.08 it is planned to deprecate the following nine rte_eth_dev_*
functions and move them into the ixgbe PMD:
``rte_eth_dev_bypass_init``, ``rte_eth_dev_bypass_state_set``,
--
2.11.0
next reply other threads:[~2017-04-18 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 15:48 Bernard Iremonger [this message]
2017-04-26 15:02 ` [PATCH] doc: postpone deprecation of functions in ethdev Mcnamara, John
2017-05-10 23:31 ` Thomas Monjalon
2017-05-10 16:22 ` Pattan, Reshma
2017-05-10 16:31 ` Ananyev, Konstantin
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=1492530536-2428-1-git-send-email-bernard.iremonger@intel.com \
--to=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.