From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Jan Blunck <jblunck@infradead.org>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] eal: deprecate 17.08 devargs API/ABI
Date: Sun, 9 Jul 2017 17:55:44 +0530 [thread overview]
Message-ID: <5ea07b58-1d6a-050c-a2ff-060608a35ab9@nxp.com> (raw)
In-Reply-To: <20170709092847.13339-3-jblunck@infradead.org>
On 7/9/2017 2:58 PM, Jan Blunck wrote:
> Add deprecation notice necessary to do devargs refactoring for 17.11.
>
> Signed-off-by: Jan Blunck <jblunck@infradead.org>
> ---
> doc/guides/rel_notes/deprecation.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 33e8b93db..5b6ed0444 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -64,3 +64,10 @@ Deprecation Notices
> be removed in 17.11:
>
> - ``rte_eal_parse_devargs_str``
> +
> +* devargs: An ABI change is planned for 17.11 for the structure ``rte_devargs``.
> + The newly introduced devargs ABI in 17.08 is tightly couple to the bus
^^^^^^^
Trivial comment: coupled
> + implementations which will get fixed in 17.11. The following function is
> + deprecated and will change API in 17.11:
> +
> + - ``rte_eal_devargs_add``
>
--
-
Shreyansh
next prev parent reply other threads:[~2017-07-09 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 9:28 [dpdk-dev] [PATCH 0/2] devargs changes / deprecation notice Jan Blunck
2017-07-09 9:28 ` [dpdk-dev] [PATCH 1/2] eal: internalize devargs parsing Jan Blunck
2017-07-09 10:28 ` Thomas Monjalon
2017-07-09 10:46 ` Jan Blunck
2017-07-09 10:56 ` Jan Blunck
2017-07-09 11:23 ` Gaëtan Rivet
2017-07-09 9:28 ` [dpdk-dev] [PATCH 2/2] eal: deprecate 17.08 devargs API/ABI Jan Blunck
2017-07-09 12:25 ` Shreyansh Jain [this message]
2017-08-07 23:03 ` 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=5ea07b58-1d6a-050c-a2ff-060608a35ab9@nxp.com \
--to=shreyansh.jain@nxp.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).