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 A57734247D; Tue, 24 Jan 2023 16:50:40 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4F30D40150; Tue, 24 Jan 2023 16:50:40 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id 71AB8400EF for <dev@dpdk.org>; Tue, 24 Jan 2023 16:50:39 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 089AE5C0597; Tue, 24 Jan 2023 10:50:39 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 24 Jan 2023 10:50:39 -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=1674575439; x= 1674661839; bh=o3g+CzT0usUedTTbPPPmEA+HOKXzYYGBRWe9MkOmqIY=; b=j RI8+WSEBaSZT02ZiyD2o90fG4+yDNROV6oP8ZDvfs//TN5wHMYux1QsPIC9OrDIG 4g4Jst3o1I4dRPR3W2UKPEIWLdK8dTwRxFjNLLGgqidtKgJNDP1NUawFTyKaxbOL Nr283q8MdmTAe0Bve2HyKMufYHblULm20lp441rD85RGrHjo7te85WZtbeSnQjde XgbF1UMyVEvx6OGE4yAbe9WH33vr3Na+9IMiIvnvPJpx7S2uSZvCHYHpZ4rC1cS8 PxSBxlsIkl8qhVAd1y82jcKK2dkQ2JaQY9vx3NOxlUfMjFgDyte8XsV6Ybp/AOwa y5yd66plk12kUq/5m4wzQ== 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=1674575439; x= 1674661839; bh=o3g+CzT0usUedTTbPPPmEA+HOKXzYYGBRWe9MkOmqIY=; b=J 304cBNixH0ih+wQhmZTO7kIKiR2lm0CuerxOQmFYyCG9LGrvl/7k3toY9po+9J9+ QUUl3rFntKDnai3E7nz7KWaQubPUVke89it0COg+bz5qXc659CfX3MI9v/nZIMWW Fm79RyfdrCIyEniDGpmWTr5Sf1Dl1eL0AUB+gDuwA/4qtjJurCdT1eLLvfTr4gI+ k9KdjtInsO2YurEvXnhE4nwu/mk2Lf8P3C8/Arc7Qhm5wziLhkusoQ4zXUYerFse 6DcpjpyswUMFpubMkoOC/6c+idrkHax9wHSDPirInMCrqRdgyzH9lSltoyNS7rSu obMDEMjRz2kriRNvawuYw== X-ME-Sender: <xms:Tv7PY2co4SyrXGSFDmoL0LxNMIIO9XWpoUfSwJ6QN7dDJj50dh0x0Q> <xme:Tv7PYwPaFD9uzr-QOrLGbQY_SInXrsOtqPXVTynVfYL4E9ncJehVApGlGcG8n2-Fy NvNdZot33urp9NfGA> X-ME-Received: <xmr:Tv7PY3jd4yNUdj2NFVnaTTF6F3gXP9gFWYRZiqNaT0ZukcaxB6J0L-XOEaoIVGtutqxh3VD9Vy2w91vzEdkFDO7drA> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedruddvtddgjeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvfevufffkfgjfhgggfgtsehtuf ertddttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghs sehmohhnjhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnheptdejieeifeehtdffgf dvleetueeffeehueejgfeuteeftddtieekgfekudehtdfgnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonh drnhgvth X-ME-Proxy: <xmx:Tv7PYz-IgoC5GAz-gT73QM2hbVMeSXwRA8yrspIdKza1F1i7prYhoQ> <xmx:Tv7PYythVHZWaueZoRU7JmOn2LO5zX0GmGqf_a3lhHGmWfZKBEtBiw> <xmx:Tv7PY6GdxI_sH8LA9uG1LI_II7LvHh-sHAXw5evNgK8GKewVFpKJlA> <xmx:T_7PY2K2LFN7CA8VsXlOTAT6cl_fd-aDJBp7y-B9qs63KnD5f-ytrQ> Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 24 Jan 2023 10:50:38 -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 v7 4/5] drivers: mlx5 use rte thread set name Date: Tue, 24 Jan 2023 16:50:37 +0100 Message-ID: <84019947.BzKH3j3Lxt@thomas> In-Reply-To: <1674502774-20253-5-git-send-email-roretzla@linux.microsoft.com> References: <1670439617-9054-1-git-send-email-roretzla@linux.microsoft.com> <1674502774-20253-1-git-send-email-roretzla@linux.microsoft.com> <1674502774-20253-5-git-send-email-roretzla@linux.microsoft.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 <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 23/01/2023 20:39, Tyler Retzlaff: > Use the new internal rte_thread_set_name API instead of the now > deprecated rte_thread_setname API. I think it should be squashed with the first patch, while introducing the new function.