DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Gaetan Rivet <gaetan.rivet@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce deprecation of flow copy function
Date: Tue, 7 Aug 2018 16:35:38 +0200	[thread overview]
Message-ID: <b007b591-ebf0-bdd6-4773-23f9cd716222@redhat.com> (raw)
In-Reply-To: <20180803143728.15817-1-adrien.mazarguil@6wind.com>



On 08/03/2018 04:37 PM, Adrien Mazarguil wrote:
> Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
> Cc: Thomas Monjalon <thomas@monjalon.net>
> Cc: Ferruh Yigit <ferruh.yigit@intel.com>
> Cc: Gaetan Rivet <gaetan.rivet@6wind.com>
> ---
>   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 14714fe94..05c77da65 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -68,3 +68,10 @@ Deprecation Notices
>     - ``rte_pdump_set_socket_dir`` will be removed;
>     - The parameter, ``path``, of ``rte_pdump_init`` will be removed;
>     - The enum ``rte_pdump_socktype`` will be removed.
> +
> +* ethdev: flow API function ``rte_flow_copy()`` will be deprecated in v18.11
> +  in favor of ``rte_flow_conv()`` (which will appear in that version) and
> +  subsequently removed for v19.02.
> +
> +  This is due to a lack of flexibility and reliance on a type unusable with
> +  C++ programs (struct rte_flow_desc).
> 

Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>

  parent reply	other threads:[~2018-08-07 14:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-03 14:37 Adrien Mazarguil
2018-08-05 21:50 ` Thomas Monjalon
2018-08-07 14:35 ` Maxime Coquelin [this message]
2018-08-08  3:11 ` Jerin Jacob
2018-08-08 22:38   ` 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=b007b591-ebf0-bdd6-4773-23f9cd716222@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=gaetan.rivet@6wind.com \
    --cc=nhorman@tuxdriver.com \
    --cc=thomas@monjalon.net \
    /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).