From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: usages issue with external mempool
Date: Wed, 27 Jul 2016 15:35:18 +0200
Message-ID: <2462423.EsoJo7cWtt@xps13>
References: <DB5PR04MB1605210D71D8CA61C01C78B6890E0@DB5PR04MB1605.eurprd04.prod.outlook.com>
 <1626416.VyKLPpZHgH@xps13>
 <DB5PR04MB1605426413A7F750D3073004890F0@DB5PR04MB1605.eurprd04.prod.outlook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
 David Hunt <david.hunt@intel.com>, dev@dpdk.org,
 "olivier.matz@6wind.com" <olivier.matz@6wind.com>,
 "viktorin@rehivetech.com" <viktorin@rehivetech.com>,
 Shreyansh Jain <shreyansh.jain@nxp.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47])
 by dpdk.org (Postfix) with ESMTP id 93E7C558A
 for <dev@dpdk.org>; Wed, 27 Jul 2016 15:35:20 +0200 (CEST)
Received: by mail-wm0-f47.google.com with SMTP id o80so62891639wme.1
 for <dev@dpdk.org>; Wed, 27 Jul 2016 06:35:20 -0700 (PDT)
In-Reply-To: <DB5PR04MB1605426413A7F750D3073004890F0@DB5PR04MB1605.eurprd04.prod.outlook.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

2016-07-27 13:23, Hemant Agrawal:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > 2016-07-27 15:21, Jerin Jacob:
> > > If we agree on this then may be I can send the API deprecation notices
> > > for rte_mempool_create for v16.11
> > 
> > It would have been a lot better to send a patch during the 16.07 cycle to avoid
> > breaking again the API.
> > I'm afraid it will even be too late for the deprecation notice.
> 
> [Hemant] Yes! It is late. 
>  we can make these changes immediately after 16.07.

You cannot change the API in 16.11 without having a deprecation agreement
in 16.07.