From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 214B041B82;
	Mon, 30 Jan 2023 16:47:01 +0100 (CET)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id A7D6F40DFB;
	Mon, 30 Jan 2023 16:47:00 +0100 (CET)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id EFF2D40DF6
 for <dev@dpdk.org>; Mon, 30 Jan 2023 16:46:58 +0100 (CET)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.47])
 by mailout.nyi.internal (Postfix) with ESMTP id 3BB265C0052;
 Mon, 30 Jan 2023 10:46:57 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162])
 by compute6.internal (MEProxy); Mon, 30 Jan 2023 10:46:57 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 cc:cc:content-transfer-encoding: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=fm3; t=1675093617; x=
 1675180017; bh=Mw8fyXo5gIOrSwH/ltUbjbqAXpyp1tDfsJ8cxVYWDnY=; b=X
 udLbodcJlnROwhf8NbL/KKs7H7RcDjlTV/kasRf0UK3KXv1T/A/bRxDU5Z03RkaM
 GOAaWTKYIWJ20hkD5UNVSQ3I+nahKN3gP/CYVth4j/a75Lv6jr6JnC2s4n4WrAMu
 Jq8MAdWQEOLiHZ/vMeL8EpbgvBD4dNGfUEEyROiMiVi/beraHN7XdEFpgdCyk6J0
 9+xZx1eoSLqG46UZDyDSA59nmzcYUbC3v29Q5q6HgH12BvCmADT7ZfNPaZnx6OYu
 jBstvls6mublSKrIbko6kN9JT+RzuE5FauVxZ+01Gm8s+UYSqGGF3x4SbmDsCucL
 t6Cvn8qZNLgxdpVxSzqTA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:cc:content-transfer-encoding
 :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=fm3; t=1675093617; x=
 1675180017; bh=Mw8fyXo5gIOrSwH/ltUbjbqAXpyp1tDfsJ8cxVYWDnY=; b=e
 hu00++U/8bLljwPHiRLTfYHUisHeUTbQMS37OrZl6iFD7UF0fIQ9DO7RLFtz/Dqc
 sOzIgHSm39dVu7oZTmNTejjbveyry3AJYOUWAiQQDUmgyqsPAHtIGcBGd0q7QjS2
 YxAXPYTvHbH+oVVkWw+W+TvWqqIG/qoKbTRQfVykUVEiNrQrmz0xK7RSC1gBY5Fb
 qj9fy640l6CpXLlShXcCDgYHuUZOGSkC3BDFrw/kuupSUC+jKtasGLkNjw5WLwD1
 alcfvz3QU22vGdor3k91HrfZXQeY0L3+3baXYYvSFS+8yrP3gPWcuzR6JOzJDeIZ
 08Yl+UGi07veMRMSCNo9g==
X-ME-Sender: <xms:cObXYxUX1lEyxklUsmHv45dPaOO4Kzi5nyHFxjKgwPObZNaK5U9Bhw>
 <xme:cObXYxnONvY1B7XbFQkLCEMSet92WbA473L2kikRnjw7BOXIerhJeW0AwdtbcJ8Nv
 YS2TKBrwNilU1jofQ>
X-ME-Received: <xmr:cObXY9aO7LarK3SAEUTQ0ol5Ioo_2wOeDuGVCPIF1_HVj1uQOeN85aqtyk-69-IhWnuybHJWHYDUW0VRlQ7tHO105Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudefvddgkedvucetufdoteggodetrfdotf
 fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
 uceurghilhhouhhtmecufedttdenucenucfjughrpefhvfevufffkfgjfhgggfgtsehtqh
 ertddttddunecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghs
 sehmohhnjhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnhepfefhjeeluedvvedtud
 dtuedtvefhieejtefhffeujefhteduudevtdektdeikeffnecuvehluhhsthgvrhfuihii
 vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonh
 drnhgvth
X-ME-Proxy: <xmx:cObXY0WBOPGCj0Z7NrotZ4QNwlMThYYgDXv7yzT1gwNGhfEVhuWQSQ>
 <xmx:cObXY7nMErcZiIw_llU9EV7Y10FaoyRmayfgxQYXIQj4ZSModmkwPQ>
 <xmx:cObXYxf9YYAHhb8ScEi5mzjduracrtILJoOzjp1WSGVBVoZ8hHV_zA>
 <xmx:cebXY5hOziuofK0ryVL4zlr0LpfoJ1tCpWNYuyN6Fd_5tlmegglBgA>
Feedback-ID: i47234305:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon,
 30 Jan 2023 10:46:56 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: dev@dpdk.org, david.marchand@redhat.com, jerinjacobk@gmail.com,
 mb@smartsharesystems.com
Subject: Re: [PATCH v10 4/4] eal: deprecation notice for rte thread setname API
Date: Mon, 30 Jan 2023 16:46:54 +0100
Message-ID: <2954281.hTDNKPQEx9@thomas>
In-Reply-To: <1674583941-16964-5-git-send-email-roretzla@linux.microsoft.com>
References: <1670439617-9054-1-git-send-email-roretzla@linux.microsoft.com>
 <1674583941-16964-1-git-send-email-roretzla@linux.microsoft.com>
 <1674583941-16964-5-git-send-email-roretzla@linux.microsoft.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

Hi,

The title should start with a verb.
I suppose it can be fixed while merging with a title like:
doc: announce deprecation of thread naming function


24/01/2023 19:12, Tyler Retzlaff:
> Notify deprecation of rte_thread_setname API, it will be removed as it
> exposes platform-specific thread details. The functionality it provided
> is now available via the new rte_lcore_set_name API.
>=20
> Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
> Acked-by: Morten Br=F8rup <mb@smartsharesystems.com>
> Acked-by: David Marchand <david.marchand@redhat.com>
> ---
> +* eal: The function ``rte_thread_setname`` is planned to be deprecated
> +  starting with the 23.07 release subject to the replacement API
> +  rte_thread_set_name being marked as stable and planned to be removed
> +  by the 23.11 release.

Minor: it would be clearer if adding some commas after "release" and "stabl=
e".


=46or the series,
Acked-by: Thomas Monjalon <thomas@monjalon.net>