From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E628E20559; Thu, 20 Jul 2017 07:26:38 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 20 Jul 2017 07:26:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=R6uIt83NJfp5vLV CnkkUugJY8Xz87ieYchuercahqD8=; b=omY30ysRSqF0pNxVwEa5A2zgfXRvlfE Y+S/M12+6fbjX5+s/Ol0b3WCWW5fvaTsBSjQ+Z8KiX58mLcX2XMhxiD3NBKQG/lo ZU6q3GNBQ0TIUuTtqoMYNLc3gRWIt7KgTjfEDRu9sBCam671fhFJfGvAN2FrIeHu yEJiQBvuhKQ4= 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-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=R6uIt83NJfp5vLVCnkkUugJY8Xz87ieYchuercahqD8=; b=mq8xNHmc G0k+zjLNqrgvrjgKKT/N2tLREq6oblHlsTKXqolXtwh6ACNCCMbyXvUqLtx9xjCc e+tAwuywC6rMNMQPF6GAA/sKUEEC4ekcx/aRqZ9EA9i9lkF4luUQXPuHu5jKUegb GRcjd5/iXeeX2D8jRJkBhY6GfwEVF0yYCpWge/1Sd40ejadL+sEdL/nGrp1+P9mY tbxakBmQsX0OMqtegI6KnENkFWZKhhyuk5BdyxA1nt6pyPsfimzB3c0ssbqnam0R 6XVltUQjdnGKtgCyh3GgfSjyVsH+y4/uLY95muxyVnzFtojyqoyieiwB2AXITp/J aRvlCy5rNwL9Pg== X-ME-Sender: X-Sasl-enc: mu0ooRAi3cvlE7xAMNOdv9WclPEVcjZfXTf3iFaeFh6e 1500549998 Received: from xps.localnet (unknown [193.47.165.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 8063F24317; Thu, 20 Jul 2017 07:26:38 -0400 (EDT) From: Thomas Monjalon To: santosh Cc: Olivier Matz , dev@dpdk.org, jerin.jacob@caviumnetworks.com Date: Thu, 20 Jul 2017 14:26:35 +0300 Message-ID: <4920445.JIvm8nXJvS@xps> In-Reply-To: References: <20170713091231.13314-1-santosh.shukla@caviumnetworks.com> <20170720104619.06a5921f@platinum> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] mempool: add notice to change mempool API/ABI 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, 20 Jul 2017 11:26:39 -0000 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.