From: Gaetan Rivet <gaetan.rivet@6wind.com>
To: dev@dpdk.org
Cc: Gaetan Rivet <gaetan.rivet@6wind.com>
Subject: [dpdk-dev] [PATCH v2 5/6] doc: update detachable flag deprecation notice
Date: Tue, 24 Oct 2017 12:35:41 +0200 [thread overview]
Message-ID: <01f9eb001ad93d611e08d8230b3da58187415e13.1508840586.git.gaetan.rivet@6wind.com> (raw)
In-Reply-To: <cover.1508840456.git.gaetan.rivet@6wind.com>
In-Reply-To: <409639fdf67753288cff5bf7d91f725666ff5678.1508840586.git.gaetan.rivet@6wind.com>
Remove the deprecation notice as the flag has been removed.
Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
---
doc/guides/rel_notes/deprecation.rst | 8 --------
1 file changed, 8 deletions(-)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 52058f5..354cc1c 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -56,14 +56,6 @@ Deprecation Notices
Target release for removal of the legacy API will be defined once most
PMDs have switched to rte_flow.
-* ethdev: The device flag advertizing hotplug capability
- ``RTE_ETH_DEV_DETACHABLE`` is not needed anymore and will be removed in
- v17.11.
- This capability is verified upon calling the relevant hotplug functions in EAL
- by checking that the ``unplug`` ops is set in the bus. This verification is
- done by the EAL and not by the ``ethdev`` layer anymore. Users relying on this
- flag being present only have to remove their checks to follow the change.
-
* ethdev: new parameters - ``rte_security_capabilities`` and
``rte_security_ops`` will be added to ``rte_eth_dev_info`` and
``rte_eth_dev`` respectively to support security operations like
--
2.1.4
next prev parent reply other threads:[~2017-10-24 10:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 8:59 [dpdk-dev] [PATCH v1 0/3] Remove RTE_ETH_DEV_DETACHABLE Gaetan Rivet
2017-10-24 8:59 ` [dpdk-dev] [PATCH v1 1/3] ethdev: remove detachable device flag Gaetan Rivet
2017-10-24 9:13 ` Andrew Rybchenko
2017-10-24 9:23 ` Thomas Monjalon
2017-10-24 9:27 ` Gaëtan Rivet
2017-10-24 8:59 ` [dpdk-dev] [PATCH v1 2/3] doc: follow detachable flag disappearance Gaetan Rivet
2017-10-25 8:55 ` Mcnamara, John
2017-10-25 8:56 ` Mcnamara, John
2017-10-24 8:59 ` [dpdk-dev] [PATCH v1 3/3] pci: propagate PMD removal error value for unplug Gaetan Rivet
2017-10-24 10:35 ` [dpdk-dev] [PATCH v2 0/6] Remove RTE_ETH_DEV_DETACHABLE Gaetan Rivet
2017-10-24 10:35 ` [dpdk-dev] [PATCH v2 1/6] ethdev: do not rely on detachable flag in detach Gaetan Rivet
2017-10-24 10:35 ` [dpdk-dev] [PATCH v2 2/6] ethdev: remove detachable device flag Gaetan Rivet
2017-10-24 10:35 ` [dpdk-dev] [PATCH v2 3/6] pci: propagate PMD removal error value for unplug Gaetan Rivet
2017-10-24 10:35 ` [dpdk-dev] [PATCH v2 4/6] doc: follow detachable flag disappearance Gaetan Rivet
2017-10-25 8:57 ` Mcnamara, John
2017-10-24 10:35 ` Gaetan Rivet [this message]
2017-10-25 9:03 ` [dpdk-dev] [PATCH v2 5/6] doc: update detachable flag deprecation notice Mcnamara, John
2017-10-24 10:35 ` [dpdk-dev] [PATCH v2 6/6] doc: note ether API change for detachable flag Gaetan Rivet
2017-10-25 8:58 ` Mcnamara, John
2017-10-25 9:01 ` Mcnamara, John
2017-10-24 12:35 ` [dpdk-dev] [PATCH v2 0/6] Remove RTE_ETH_DEV_DETACHABLE Thomas Monjalon
2017-10-25 17:37 ` Ferruh Yigit
2017-10-30 9:45 ` Alejandro Lucero
2017-10-31 11:09 ` Alejandro Lucero
2017-10-31 17:24 ` Ferruh Yigit
2017-10-24 23:56 ` Ferruh Yigit
2017-10-25 16:11 ` 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=01f9eb001ad93d611e08d8230b3da58187415e13.1508840586.git.gaetan.rivet@6wind.com \
--to=gaetan.rivet@6wind.com \
--cc=dev@dpdk.org \
/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).