From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v7 0/6] Add lock-free ring and mempool handler
Date: Tue, 19 Mar 2019 08:51:23 -0700
Message-ID: <20190319085123.00df99c2@shemminger-XPS-13-9360>
References: <20190306150342.2894-1-gage.eads@intel.com>
 <20190318213555.17345-1-gage.eads@intel.com>
 <9184057F7FC11744A2107296B6B8EB1E54207FC7@FMSMSX108.amr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "dev@dpdk.org" <dev@dpdk.org>, "olivier.matz@6wind.com"
 <olivier.matz@6wind.com>, "arybchenko@solarflare.com"
 <arybchenko@solarflare.com>, "Richardson, Bruce"
 <bruce.richardson@intel.com>, "Ananyev, Konstantin"
 <konstantin.ananyev@intel.com>, "jerinj@marvell.com" <jerinj@marvell.com>,
 "mczekaj@marvell.com" <mczekaj@marvell.com>, "nd@arm.com" <nd@arm.com>,
 "Ola.Liljedahl@arm.com" <Ola.Liljedahl@arm.com>
To: "Eads, Gage" <gage.eads@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pf1-f193.google.com (mail-pf1-f193.google.com
 [209.85.210.193]) by dpdk.org (Postfix) with ESMTP id D0435A3
 for <dev@dpdk.org>; Tue, 19 Mar 2019 16:51:27 +0100 (CET)
Received: by mail-pf1-f193.google.com with SMTP id v64so14000413pfb.1
 for <dev@dpdk.org>; Tue, 19 Mar 2019 08:51:27 -0700 (PDT)
In-Reply-To: <9184057F7FC11744A2107296B6B8EB1E54207FC7@FMSMSX108.amr.corp.intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Mon, 18 Mar 2019 21:49:44 +0000
"Eads, Gage" <gage.eads@intel.com> wrote:

> Hi all,
> 
> Friendly reminder that in order to get this feature into 19.08 (assuming folks also want that :)), the API deprecation notice needs to be merged into 19.05.
> 
> Thanks,
> Gage

Given the recent API/ABI stability discussion, this is the kind of patch that really
needs to be examined and justified.