From: Gaetan Rivet <gaetan.rivet@6wind.com>
To: dev@dpdk.org
Cc: Jan Blunck <jblunck@infradead.org>
Subject: [dpdk-dev] [PATCH 1/2] pci: deprecate PCI detach
Date: Wed, 10 May 2017 14:52:04 +0200 [thread overview]
Message-ID: <4b1edeb12ff61bdb04a0189be30395589c713dbb.1494420483.git.gaetan.rivet@6wind.com> (raw)
This patch deprecates the function rte_eal_pci_detach in 17.05,
which will be removed in 17.08.
The generic detach bus method should be used instead.
Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: Jan Blunck <jblunck@infradead.org>
---
doc/guides/rel_notes/deprecation.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index a3e7c72..c2f58eb 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -81,3 +81,9 @@ Deprecation Notices
- ``rte_crpytodev_scheduler_mode_get``, replaced by ``rte_cryptodev_scheduler_mode_get``
- ``rte_crpytodev_scheduler_mode_set``, replaced by ``rte_cryptodev_scheduler_mode_set``
+
+* pci: The following function is deprecated starting from 17.05 and will be
+ removed in 17.08:
+
+ - ``rte_eal_pci_detach``, replaced by using the corresponding bus generic
+ method ``detach``.
--
2.1.4
next reply other threads:[~2017-05-10 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 12:52 Gaetan Rivet [this message]
2017-05-10 12:52 ` [dpdk-dev] [PATCH 2/2] devargs: announce ABI change for device parameters Gaetan Rivet
2017-05-10 13:04 ` Thomas Monjalon
2017-05-10 13:02 ` [dpdk-dev] [PATCH 1/2] pci: deprecate PCI detach Thomas Monjalon
2017-05-10 15:48 ` Gaëtan Rivet
2017-05-10 15:46 ` [dpdk-dev] [PATCH v2] devargs: announce ABI change for device parameters Gaetan Rivet
2017-05-10 17:28 ` Jerin Jacob
2017-05-10 17:54 ` Stephen Hemminger
2017-05-10 21:59 ` Gaëtan Rivet
2017-05-10 18:50 ` David Marchand
2017-05-10 19:54 ` Maxime Coquelin
2017-05-10 23:14 ` 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=4b1edeb12ff61bdb04a0189be30395589c713dbb.1494420483.git.gaetan.rivet@6wind.com \
--to=gaetan.rivet@6wind.com \
--cc=dev@dpdk.org \
--cc=jblunck@infradead.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).