From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH 1/2] mempool: remove deprecated functions Date: Fri, 27 Jul 2018 16:38:56 +0200 Message-ID: <11107367.P76Ua8LdDk@xps> References: <1531306750-9844-1-git-send-email-arybchenko@solarflare.com> <5677276.1WdofzzUsl@xps> <217aa1df-7b7e-bad0-2db5-928349b018cc@solarflare.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Olivier Matz To: Andrew Rybchenko Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id A0FB45592 for ; Fri, 27 Jul 2018 16:39:01 +0200 (CEST) In-Reply-To: <217aa1df-7b7e-bad0-2db5-928349b018cc@solarflare.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" 27/07/2018 15:45, Andrew Rybchenko: > On 27.07.2018 00:34, Thomas Monjalon wrote: > > 11/07/2018 12:59, Andrew Rybchenko: > >> Functions rte_mempool_populate_phys(), rte_mempool_virt2phy() and > >> rte_mempool_populate_phys_tab() are just wrappers for corresponding > >> IOVA functions and were deprecated in v17.11. > >> > >> Functions rte_mempool_xmem_create(), rte_mempool_xmem_size(), > >> rte_mempool_xmem_usage() and rte_mempool_populate_iova_tab() were > >> deprecated in v18.05 and removal was announced earlier in v18.02. > >> > >> Signed-off-by: Andrew Rybchenko > >> --- > >> lib/librte_mempool/Makefile | 3 - > >> lib/librte_mempool/meson.build | 4 - > >> lib/librte_mempool/rte_mempool.c | 181 +-------------------- > >> lib/librte_mempool/rte_mempool.h | 179 -------------------- > >> lib/librte_mempool/rte_mempool_version.map | 6 - > >> 5 files changed, 1 insertion(+), 372 deletions(-) > > Please update the release notes, deprecation notice, and bump ABI version. > > Will do. Deprecation notice which schedules removal of xmem functions > was removed on previous release when these function are deprecated. > Is it a problem? Should removal of already deprecated function pass > deprecation (removal) announcement procedure once again? No, it's OK. We should have left the notice about removal but it's too late :)