DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
Cc: dev@dpdk.org, Olivier Matz <olivier.matz@6wind.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Neil Horman <nhorman@tuxdriver.com>,
	andrey.chilikin@intel.com, adrien.mazarguil@6wind.com
Subject: Re: [dpdk-dev] [PATCH v3] doc: ethdev ABI change deprecation notice
Date: Wed, 14 Feb 2018 01:14:52 +0100	[thread overview]
Message-ID: <1552586.93IePh6r2W@xps> (raw)
In-Reply-To: <20180213132102.c5nzho3nawni2u3q@platinum>

> > >> Signed-off-by: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
> > >>
> > >> Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
> > >> ---
> > >> +* ethdev: announce ABI change
> > >> +  The size of variables flow_types_mask in rte_eth_fdir_info structure,
> > >> +  sym_hash_enable_mask and valid_bit_mask in rte_eth_hash_global_conf structure
> > >> +  will be increased from 32 to 64 bits to fulfill hardware requirements.
> > >> +  This change will break existing ABI as size of the structures will increase.
> > >> +
> > > Acked-by: Neil Horman <nhorman@tuxdriver.com>
> > 
> > Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
> 
> Acked-by: Olivier Matz <olivier.matz@6wind.com>

Acked-by: Thomas Monjalon <thomas@monjalon.net>

I would prefer you drop the legacy code to keep only rte_flow.

  reply	other threads:[~2018-02-14  0:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 14:47 [dpdk-dev] [PATCH] " Kirill Rybalchenko
2018-01-12 10:19 ` Kovacevic, Marko
2018-01-12 10:27 ` [dpdk-dev] [PATCH v2] " Kirill Rybalchenko
2018-01-12 10:29   ` [dpdk-dev] [PATCH v3] " Kirill Rybalchenko
2018-01-12 14:38     ` Neil Horman
2018-02-13 12:09       ` Ferruh Yigit
2018-02-13 13:21         ` Olivier Matz
2018-02-14  0:14           ` Thomas Monjalon [this message]
2018-02-14 17:18             ` 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=1552586.93IePh6r2W@xps \
    --to=thomas@monjalon.net \
    --cc=adrien.mazarguil@6wind.com \
    --cc=andrey.chilikin@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=kirill.rybalchenko@intel.com \
    --cc=nhorman@tuxdriver.com \
    --cc=olivier.matz@6wind.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).