From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 6B3294C74
 for <dev@dpdk.org>; Thu,  8 Mar 2018 09:05:45 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id CB7A121B07;
 Thu,  8 Mar 2018 03:05:44 -0500 (EST)
Received: from frontend1 ([10.202.2.160])
 by compute1.internal (MEProxy); Thu, 08 Mar 2018 03:05:44 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 cc:content-transfer-encoding:content-type:date:from:in-reply-to
 :message-id:mime-version:references:subject:to:x-me-sender
 :x-me-sender:x-sasl-enc; s=mesmtp; bh=mIsXwcQQ1oTkLnj8tO1YIWOHCM
 NolCPexkd25XxzfiE=; b=gawYa+PWNEGCpzAj202kFA4x7nwidQbIR1Q4AREI6L
 04qgeWR82LOJL/xm2XjRk+3BHXpiI3GzYEfPb7v8pzwTVb7jYbn8cITxfpm5sBGu
 mYJEiBtujzHdkH6+7hEGVv9WJaNtD3B/WqpscqrBVJBd3KjR6GMYo/nwnaVBO7o7
 8=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=mIsXwc
 QQ1oTkLnj8tO1YIWOHCMNolCPexkd25XxzfiE=; b=St/bVV5cYO8L52ZzRzfOEr
 ef6LtOrJcJjovdOprOK3/YbXps8KLhUQ9wyBjxBdt6qw8uqeF7UcTpLFq5Gz1wws
 vIM2QYeSEHedWK+6fED0nNDocpM0XaGmmAyfXwp12x4MMnlag9e0ZjvRdNJlkyEH
 k95sy6mc4Ej2riWk5REojaEMKLCKX6H7IgMdnnNalyJJks81v0jq5XBcgfEaMOBy
 fcLd4ZQljmmZGv35sfM9Moo5nZtQt3sLl86D+7QHeJXEhwe63cmcIMqp+Idggvxt
 1DF8XZhGvM9kYvJ5CkSXoMn5a2vPhDcm4vD1NwjS8q/+lr87gIcx+2LWgxhwZ36Q
 ==
X-ME-Sender: <xms:2O6gWoHIrbZMbXKLsucYSjQT7ESwhmpREcRzyBQ7KprSbsjE_Y12LQ>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id CD0D77E46B;
 Thu,  8 Mar 2018 03:05:43 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
 John McNamara <john.mcnamara@intel.com>,
 Marko Kovacevic <marko.kovacevic@intel.com>, dev@dpdk.org,
 Luca Boccassi <bluca@debian.org>,
 Christian Ehrhardt <christian.ehrhardt@canonical.com>
Date: Thu, 08 Mar 2018 09:05:18 +0100
Message-ID: <6880912.l9NoFy8GUE@xps>
In-Reply-To: <20180307174422.118291-1-ferruh.yigit@intel.com>
References: <20180307174422.118291-1-ferruh.yigit@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [RFC] config: remove RTE_NEXT_ABI
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://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: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2018 08:05:45 -0000

07/03/2018 18:44, Ferruh Yigit:
> After experimental API process defined do we still need RTE_NEXT_ABI
> config and process which has similar targets?

They are different targets.
Experimental API is always enabled but may be avoided by applications.
Next ABI can be used to break ABI without notice and disabled to keep
old ABI compatibility. It is almost never used because it is preferred
to keep ABI compatibility with rte_compat macros, or wait a deprecation
period after notice.