From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id 0F11F1B4FC for ; Thu, 4 Oct 2018 17:10:13 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id D6AADC43; Thu, 4 Oct 2018 11:10:11 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 04 Oct 2018 11:10:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=mn4hVRt0gSciWCroATHRhITaTRH83FEnhjoTPqs5qPI=; b=m9rSjRBhFi7P xstmJ3eD0j4QiK0JmQwuF9iskNYIAONfpeCGffexxXSQEsw7jNgvZatWponMFw/C Z6l4MkAFzEkOL/1pCBHAZZY992Hqxg6fA8Wt97uSMkWjLAgNMLxZ+IyD8bk6lsQ4 Froj6B+/KHhnV0qRhMrKKGBVok0HDhk= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=mn4hVRt0gSciWCroATHRhITaTRH83FEnhjoTPqs5q PI=; b=g3xorBMmu0fGuaSXDOo2da1pk4CYbi7dZ64xJQvlQSlULrGyMwSwu3e5j 4N8rns5EhzPnPwH+3atz1jZQFjSNumnve4cx6FHtxveTx02aWFb0JUtb1wiqzPha 0OhB8TzlKlVcz4t4FtT1UekiX/RDRySOksxOi/oNtUexNhDPvmwu9SR3JbYf6QoE Nj3ZZV1jogbqHnCwzmnYnFWe1hlUwmQ//spNq0O/fjT2MHxUxUP7JheNXpgWhIK7 Ta7thyc50pj3KFd65rP/t2CEyGHof1nxVoBRObfzr/LckI8N4rqOdN/YBMrS2xZr YDtrhYj8zZMjxSdFUwSEZdk9/frvw== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 430DB102F3; Thu, 4 Oct 2018 11:10:10 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: dev@dpdk.org, Neil Horman , Luca Boccassi , Christian Ehrhardt Date: Thu, 04 Oct 2018 17:10:09 +0200 Message-ID: <1785611.eL8Z1dKoq2@xps> In-Reply-To: <20181004154829.66523-1-ferruh.yigit@intel.com> References: <20181004154306.65867-1-ferruh.yigit@intel.com> <20181004154829.66523-1-ferruh.yigit@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2] config: disable RTE_NEXT_ABI by default X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Oct 2018 15:10:13 -0000 04/10/2018 17:48, Ferruh Yigit: > Enabling RTE_NEXT_ABI means to enable APIs that break the ABI for > the current release and these APIs are targeted for further release. It seems nobody is using it in last releases. > RTE_NEXT_ABI shouldn't be enabled by default. The reason for having it enabled by default is that when you build DPDK yourself, you probably want the latest features. If packaged properly for stability, it is easy to disable it in the package recipe.