From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id CB9058DAC for ; Mon, 23 Nov 2015 04:53:13 +0100 (CET) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 44B3D17A; Sun, 22 Nov 2015 22:53:13 -0500 (EST) Date: Sun, 22 Nov 2015 22:53:13 -0500 From: Matthew Hall To: Thomas Monjalon Message-ID: <20151123035313.GA31612@mhcomputing.net> References: <20151121084935.GA24056@mhcomputing.net> <2764108.ZoWOrsZgTX@xps13> <20151122232509.GA27730@mhcomputing.net> <1629381.JoeoXysOOK@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1629381.JoeoXysOOK@xps13> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] difficulty w/ RTE_NEXT_ABI X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2015 03:53:14 -0000 On Mon, Nov 23, 2015 at 01:13:32AM +0100, Thomas Monjalon wrote: > If your change is sent upstream, you must rely on the new ABI because the old one > will be removed when your change will be integrated. > If it is a local change, it depends on which ABI you want to use. I submitted separately to Bruce & Co. It is for LPM field expansion. My question what to do came up in the context of a rebase to master. > Yes. Hope my detailed answer is enough. Thanks. It is less confusing now. Matthew.