From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v1 01/16] ethdev: update ABI for flow API functions Date: Thu, 05 Apr 2018 12:06:10 +0200 Message-ID: <2170144.NMypU1fd1R@xps> References: <20180404150312.12304-1-adrien.mazarguil@6wind.com> <20180404150312.12304-2-adrien.mazarguil@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Ferruh Yigit To: Adrien Mazarguil Return-path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id AEE4F1CA74 for ; Thu, 5 Apr 2018 12:06:11 +0200 (CEST) In-Reply-To: <20180404150312.12304-2-adrien.mazarguil@6wind.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" 04/04/2018 17:56, Adrien Mazarguil: > Subsequent patches will modify existing types and slightly alter the > behavior of the flow API. This warrants a major ABI breakage. > > While it is already taken care of for 18.05 (LIBABIVER was updated to > version 9 by a prior commit), this patch explicitly adds the affected flow > API functions as a safety measure. I don't understand this patch. If the API is broken, you must move the function from old block to the new one. And it must be done in the patch modifying the function. > --- a/lib/librte_ether/rte_ethdev_version.map > +++ b/lib/librte_ether/rte_ethdev_version.map > +DPDK_18.05 { > + global: > + > + rte_flow_validate; > + rte_flow_create; > + rte_flow_query; > + rte_flow_copy; > + > +} DPDK_18.02;