From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v4 3/3] doc: add deprecation marker usage Date: Fri, 1 Feb 2019 17:06:32 +0000 Message-ID: <9400e996-2f6e-d3da-9c95-06e8a42087fd@intel.com> References: <20190122162310.53613-1-ferruh.yigit@intel.com> <20190124181019.17168-1-ferruh.yigit@intel.com> <20190124181019.17168-3-ferruh.yigit@intel.com> <3155698.1yX0fgTuye@xps> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: dev@dpdk.org, John McNamara , Marko Kovacevic , Luca Boccassi , Kevin Traynor , Yongseok Koh , Neil Horman To: Thomas Monjalon Return-path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 5C7F91B4F0 for ; Fri, 1 Feb 2019 18:06:36 +0100 (CET) In-Reply-To: <3155698.1yX0fgTuye@xps> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 1/31/2019 5:17 PM, Thomas Monjalon wrote: >> + >> +Reminder that new API should follow deprecation process to be able to replace old API. > This last sentence is not clear to me. > I think you mean the old API should follow deprecation process > to be removed (replaced). Yes, we are trying to say same thing. Deprecation process required for replacing API.