DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
	dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
	David Marchand <david.marchand@redhat.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Jerin Jacob <jerinjacobk@gmail.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce remove of unused enum in ACL library
Date: Thu, 06 Aug 2020 19:24:08 +0200	[thread overview]
Message-ID: <11943140.JLvrrvRiZU@thomas> (raw)
In-Reply-To: <CALBAE1MW__hih1Bb9yEyDxskQyj2dgs2vnm60r-xy30rCFbVcQ@mail.gmail.com>

06/08/2020 19:06, Jerin Jacob:
> On Thu, Aug 6, 2020 at 10:36 PM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > On Thu, Aug 06, 2020 at 06:37:20PM +0200, Thomas Monjalon wrote:
> > > 06/08/2020 14:57, Ferruh Yigit:
> > > > 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>
> > > > > ---
> > > > > +* 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>
> > >
> > > Acked-by: Thomas Monjalon <thomas@monjalon.net>
> > >
> > Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> 
> Acked-by: Jerin Jacob <jerinj@marvell.com>

Applied




      reply	other threads:[~2020-08-06 17:24 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
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 [this message]

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=11943140.JLvrrvRiZU@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jerinjacobk@gmail.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=stephen@networkplumber.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).