DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: announce remove of unused enum in ACL library
Date: Thu, 6 Aug 2020 13:57:25 +0100	[thread overview]
Message-ID: <07e6b902-35d9-c94f-d855-518dd7aae86a@intel.com> (raw)
In-Reply-To: <20200806122337.1562-1-konstantin.ananyev@intel.com>

On 8/6/2020 1:23 PM, Konstantin Ananyev wrote:
> Announce removal of unused enum value (RTE_ACL_CLASSIFY_NUM).
> 
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 1a07f8817..fd0168b23 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -232,3 +232,7 @@ Deprecation Notices
>    Python 2 support will be completely removed in 20.11.
>    In 20.08, explicit deprecation warnings will be displayed when running
>    scripts with Python 2.
> +
> +* acl: ``RTE_ACL_CLASSIFY_NUM`` enum value will be removed. This enum
> +  value is not used inside DPDK, while it prevents to add new classify
> +  algorithms without causing an ABI breakage.
> 

Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

  reply	other threads:[~2020-08-06 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 12:23 Konstantin Ananyev
2020-08-06 12:57 ` Ferruh Yigit [this message]
2020-08-06 16:37   ` Thomas Monjalon
2020-08-06 17:05     ` Bruce Richardson
2020-08-06 17:06       ` Jerin Jacob
2020-08-06 17:24         ` 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=07e6b902-35d9-c94f-d855-518dd7aae86a@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@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 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).