From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] drivers: update DPAA2 libs ABIVER and build reproducibility Date: Tue, 10 Oct 2017 17:48:07 +0200 Message-ID: <5377044.W38hQe7MOC@xps> References: <1507644941-21660-1-git-send-email-hemant.agrawal@nxp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, ferruh.yigit@intel.com To: Hemant Agrawal Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 9C3301B316 for ; Tue, 10 Oct 2017 17:48:09 +0200 (CEST) In-Reply-To: <1507644941-21660-1-git-send-email-hemant.agrawal@nxp.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 10/10/2017 16:15, Hemant Agrawal: > Signed-off-by: Hemant Agrawal > --- > drivers/bus/fslmc/Makefile | 3 ++- > drivers/crypto/dpaa2_sec/Makefile | 3 ++- > drivers/event/dpaa2/Makefile | 3 ++- > drivers/mempool/dpaa2/Makefile | 3 ++- > drivers/net/dpaa2/Makefile | 3 ++- > 5 files changed, 10 insertions(+), 5 deletions(-) Why are you changing LIBABIVER in all these libs? Generally speaking, a driver should not upgrade its ABI version, because it should have no interface. The ABI version must be changed in the patch breaking the ABI. If you do it later, it must be a fix with Fixes line. This way we will have the reference to the code breaking the ABI.