From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] mempool: add notice to change mempool API/ABI Date: Thu, 20 Jul 2017 14:26:35 +0300 Message-ID: <4920445.JIvm8nXJvS@xps> References: <20170713091231.13314-1-santosh.shukla@caviumnetworks.com> <20170720104619.06a5921f@platinum> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Olivier Matz , dev@dpdk.org, jerin.jacob@caviumnetworks.com To: santosh Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 70D0E23C for ; Thu, 20 Jul 2017 13:26:39 +0200 (CEST) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 20/07/2017 12:27, santosh: > On Thursday 20 July 2017 02:16 PM, Olivier Matz wrote: > > > On Thu, 13 Jul 2017 09:12:31 +0000, Santosh Shukla wrote: > >> [PATCH] mempool: add notice to change mempool API/ABI > > I think the usual titles for these notices are more: > > > > doc: announce API/ABI changes for mempool > > in v2. > > > Ideally, the title should describe more precisely the kind of > > changes. In that particular case, it looks quite difficult, > > so just saying "mempool" looks okay. Maybe Thomas will prefer > > one entry per change, I don't know. > > > Thomas, Are you fine with approach? Yes it is OK. The important words are "announce", "API" and "mempool". As you are breaking the API, no need to be explicit about ABI.