From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 3A4891B192 for ; Mon, 14 Jan 2019 10:50:53 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id CE58729680; Mon, 14 Jan 2019 04:50:52 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 14 Jan 2019 04:50:52 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=GEUJbKqYWhYMo1SPvh7U3ffwBT1WkErnk37AXDh1HyQ=; b=jrbii+TvGpBq 7i28SeRVKFb2GPMRHxOWxZhSGum73/rwI2Dwa++xR78NBX8wCL/qTL0tw/R/f04x D9m2LWZPfHubjnl6GWWUvDjW60MunREKJs2W1j6KvuS1v1CWoNK4WDLtmobXd8GB wjjL7pRpHE/IzW8mJ2Yo2boYGZ+2gUA= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=GEUJbKqYWhYMo1SPvh7U3ffwBT1WkErnk37AXDh1H yQ=; b=IbSqkpH42yU+7ZYQw1PWDjzmSppbgXjPSzrSsKDj6MohVV+mADUgNMswV IHOs+GQ9siimjtToktNudWUOun9A06M8eT5sOHAp1/UcYSq5e+JFttt4Sbar2/f/ jmkVo/m+TWpVDA3jvXCGKcjoapBqw6bFVaZJf0rv5aFLf5JzOrTpr+bz3UQgr9fL blJ2DzWKYw1Bv9cDpGvkjyiYkWKwZZtcCK+hLJIZRoLdmPeFLfWPTw1K9coJ92W2 9a1mp25YFhld3pcuxDA+Drrg/8oGC3P68jdaeknuxZCtkIgQVp4707KpmPRRsa0M XnGuVyvnhEsUtdeEWpOvA6m0ePI0Q== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrgedugddtkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffkfgjfh gggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceo thhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukfhppeejjedrudefgedrvddtfe drudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 3E04F100B8; Mon, 14 Jan 2019 04:50:51 -0500 (EST) From: Thomas Monjalon To: Andrew Rybchenko , Yongseok Koh Cc: konstantin.ananyev@intel.com, olivier.matz@6wind.com, dev@dpdk.org Date: Mon, 14 Jan 2019 10:50:50 +0100 Message-ID: <2069315.XgEaZRbMEa@xps> In-Reply-To: <210872a4-5e85-bef3-dca1-2e468be373bb@solarflare.com> References: <20190114052055.12896-1-yskoh@mellanox.com> <210872a4-5e85-bef3-dca1-2e468be373bb@solarflare.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 1/2] mbuf: remove deprecated macro 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: Mon, 14 Jan 2019 09:50:53 -0000 14/01/2019 08:40, Andrew Rybchenko: > On 1/14/19 8:20 AM, Yongseok Koh wrote: > > RTE_MBUF_INDIRECT() is replaced with RTE_MBUF_CLONED() and removed. > > This macro was deprecated in release 18.05 when EXT_ATTACHED_MBUF was > > introduced. > > > > Signed-off-by: Yongseok Koh > > Acked-by: Andrew Rybchenko > > <...> > > > diff --git a/doc/guides/rel_notes/release_19_02.rst b/doc/guides/rel_notes/release_19_02.rst > > index 5a46f1acdc..c4ad072412 100644 > > --- a/doc/guides/rel_notes/release_19_02.rst > > +++ b/doc/guides/rel_notes/release_19_02.rst > > @@ -210,6 +210,9 @@ API Changes > > function from now on. Failed to do so will cause > > ``rte_cryptodev_sym_session_create()`` function call return error. > > > > +* mbuf: ``RTE_MBUF_INDIRECT()``, which was deprecated in 18.05, was replaced > > + with ``RTE_MBUF_CLONED()`` and removed in 19.02. > > + > > May be order in New Features should be applicable in API changes as well. Yes Usually I take care of it when applying, but would be better to be fixed in the patch itself :)