From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id BE1ED42884; Fri, 31 Mar 2023 15:20:52 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6227242D13; Fri, 31 Mar 2023 15:20:52 +0200 (CEST) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) by mails.dpdk.org (Postfix) with ESMTP id 4CEE342D12 for ; Fri, 31 Mar 2023 15:20:50 +0200 (CEST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 8458E32002D8; Fri, 31 Mar 2023 09:20:48 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Fri, 31 Mar 2023 09:20:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1680268848; x=1680355248; bh=D6Pk2mEApIB20vsmZH4zZHPonLzBrR80PBo cOK49wzA=; b=eVqsaZjAXOHOQzNMJ/YUTZHNS5kzlaYMSy4HNVYWwdkxiuF68Zu 6Z2Vjq+SuW+5dd+oW3Rnl7c9i5rEf4jrTk1judeMrigabIpdo5jN+EZst+iub848 lS2mNWo2LFSmdBUI1vR0JAqD0bSgfB+G2vJGxSvfqcl9/wP2iT/275btvVd5pgW5 0EjzE7lr07af11BpxZyaf9S+djWi3Jg4PVQ3SyZHrozJEROj+CcvBgiXb8Y7WWQn +jxzf1/4CHJXghDDhXPU+ddsEonRvxpqR+MHzcA+A3UiPTqKOczq1cTbLmI+BeRQ p1oolWafIaemJVNBxDyqgTJaScT6HPuH8ag== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1680268848; x=1680355248; bh=D6Pk2mEApIB20vsmZH4zZHPonLzBrR80PBo cOK49wzA=; b=V7HGYlvVAeyUJhYZaEM8TcPOgImB7DEk2eF7882cl4Rd92lhHNu VQNWzWj/xqwR0oTL01LKHD+HaKaX+27huaRJbKNW7BLWUyzRZG0d/wnia+b0yX/l CJylzUBa6uTeGRcAOjlPf88cyzeggE6Fs4avypA+4gm64GlfucN9HSp9p0eRhCke Y6SiFqZ7b55vQbzePL4bhPbIjdcKksMveDNVYXwMpDBerNaQ+DFwi2ya25uxIGtT ok9yBJsbsQmZ5EeglHS7cJVRz7Pm21W6eWbivR3oRE4rf7u7UjCA/2bUToSjTZs0 x+jnFHFT6OfjtcAKmmJ3Q/n2643OHm2K8tQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdeiuddgiedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 31 Mar 2023 09:20:47 -0400 (EDT) From: Thomas Monjalon To: Cristian Dumitrescu Cc: dev@dpdk.org, kamalakannan.r@intel.com, yogesh.jangra@intel.com, harshad.suresh.narayane@intel.com, bruce.richardson@intel.com Subject: Re: [PATCH V3] doc: announce the pipeline legacy API deprecation Date: Fri, 31 Mar 2023 15:20:44 +0200 Message-ID: <5760788.OBFZWjSADL@thomas> In-Reply-To: <20230309200949.847639-1-cristian.dumitrescu@intel.com> References: <20221121195421.3743179-1-cristian.dumitrescu@intel.com> <20230309200949.847639-1-cristian.dumitrescu@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 09/03/2023 21:09, Cristian Dumitrescu: > Announce the deprecation of the legacy pipeline, table and port > library API and gradual stabilization of the new API. > > Signed-off-by: Cristian Dumitrescu We'll discuss the timeline for promoting the new API, when reviewing the patches. As Bruce suggest, I anticipate it should be the first thing to do. Applied, thanks.