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 26AFF4247A; Tue, 24 Jan 2023 19:05:25 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1A92640223; Tue, 24 Jan 2023 19:05:25 +0100 (CET) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by mails.dpdk.org (Postfix) with ESMTP id 3C69D40150 for ; Tue, 24 Jan 2023 19:05:24 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 86768320091F; Tue, 24 Jan 2023 13:05:22 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 24 Jan 2023 13:05:23 -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=1674583522; x= 1674669922; bh=41tHGnW9jW+ZcVSiF6nk0RF/kMqOIqcSsNPv9OWXiYA=; b=E hPVB3FPvzlRpUPfaQgpkP5a2lGFhCts9TolKn1kflqOk5zHXr5hOBKFf623cJ0la ZArJBOB3OF6f/Y7xHXiJ9LaC0SOqCiyjSXbqjFmJdrlHHBx+Azs8olmm3AgxfoBp +/mXEuSzhkpI5vRNp3S0UZbJqKH0A0PJcEnO/opzOpfTCJYQCXbRNQFdhuGQai0x yFIuPvF0fM8gKaZypUQ7B6L99Npdv6iO4y3N9ZBIciTz559b8KYNKhlkp7gLh+Gv wrjyz5Y90c9F0F742vnu41T/G8VvvbQvOwZxfQfEBJIpY3hQDVQJuEZgBZJAjoY0 fdy2XHldaHBFaLc6MHl5Q== 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=1674583522; x= 1674669922; bh=41tHGnW9jW+ZcVSiF6nk0RF/kMqOIqcSsNPv9OWXiYA=; b=J VD7ETpNFqd++vE+tEVGXGr1VckIRKc8Okd8CpO5ZtJvrRkxFd5saYI/EhkFcNIsq MZ97DXTqsG7UdJUZCL/Pz3qtKOZtsaAxk7sj+CaTwjEl30fi8YXpWlxtS0c1K/V9 VaNFHMK/CYbMu9uLimhVePuHpvGkCwImvLOlp/qte5NAwVF4Iiuw4mlLCL/qduGH K141vdEubOsWU/8eZkEjMVah0QlHjKjDPrkFJc5z16Qb8mTJBdZll0WJQSL266YK ZNkD/tFv8/P57oGRhep5/WIZyTS298iLHa7nmsOsj59e1eWwagmgP6yd3vgmZn6r lxuEB9SC/vJ0/c0FTPplw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedruddvtddguddthecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhephffvvefufffkjghfggfgtgesth furedttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgr shesmhhonhhjrghlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpedtjeeiieefhedtff fgvdelteeufeefheeujefgueetfedttdeikefgkeduhedtgfenucevlhhushhtvghrufhi iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghloh hnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 24 Jan 2023 13:05:20 -0500 (EST) From: Thomas Monjalon To: Tyler Retzlaff Cc: dev@dpdk.org, david.marchand@redhat.com, jerinjacobk@gmail.com, mb@smartsharesystems.com Subject: Re: [PATCH v9 4/4] eal: deprecation notice for rte thread setname API Date: Tue, 24 Jan 2023 19:05:18 +0100 Message-ID: <4446470.ghgXmdF2J7@thomas> In-Reply-To: <1674583351-15292-5-git-send-email-roretzla@linux.microsoft.com> References: <1670439617-9054-1-git-send-email-roretzla@linux.microsoft.com> <1674583351-15292-1-git-send-email-roretzla@linux.microsoft.com> <1674583351-15292-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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 24/01/2023 19:02, Tyler Retzlaff: > +* eal: The function ``rte_thread_setname`` is planned to be deprecated > + starting with the 23.03 release subject to the replacement API > + rte_thread_set_name being marked as stable and planned to be removed > + by the 23.11 release. You are introducing rte_thread_set_name as experimental in 23.03. So we are supposed to wait at least a release to make it stable. Let's deprecate it in 23.07 and remove in 23.11.