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 24CAD41B82; Mon, 30 Jan 2023 17:19:40 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AC92140DF6; Mon, 30 Jan 2023 17:19:39 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id E9E8640C35 for ; Mon, 30 Jan 2023 17:19:37 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1675095577; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=myUB2EENEAHCplv33fsMd8vEev2IjuwO4YkXBBlvTt4=; b=EqHb69Rb8K32m/izQ0lLIt9aofO7iz7buRZcqCncwyYuZPhZRhVXZ8xjePwZRVY9lh4jeP xUerZX02DBbZIrohJ8k2Xch2ELBNKxw502zBJj4MuUM8aSmFU9yRGFoRpXdGiisk6OpaM3 5dEHPQNW6J8bzb1xUhavs6JA9f1InsA= Received: from mail-pf1-f200.google.com (mail-pf1-f200.google.com [209.85.210.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-622-tKWuyzUANqSTXms2nwwSEw-1; Mon, 30 Jan 2023 11:19:32 -0500 X-MC-Unique: tKWuyzUANqSTXms2nwwSEw-1 Received: by mail-pf1-f200.google.com with SMTP id n34-20020a056a000d6200b005912ead88aeso5649446pfv.3 for ; Mon, 30 Jan 2023 08:19:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=myUB2EENEAHCplv33fsMd8vEev2IjuwO4YkXBBlvTt4=; b=iUCge7BlTANVdLUn5bXw9sH2Yc28GjSbL7QonEwApYre6EI14PMdk3e3Fw3pmoljrV MZ2j3tB7j8Tq+dYdZNLE4lvU22eJn+BYvKXJFakIYixv0Ya5FAhQtu02ANKhazqTfS+7 MejcYqGmaS/sNs3G5V1iNyUnLDxjJZQv9a77nDBzTe3lcE+fFDxhggE0mtgjGwZcm0cc 2WzRh1zDH85EtpiJrAtSuPi9PzN2T9XM0JIRf7aqUI6I58aQ+vj1Ncj1RahBYlsmMx/8 Xj0s5pFHXJExD+eZ5OgpbtyaCp3c5UQegBqP9wDf860f57TRL6whkak/21cReCoUXETJ 98Yw== X-Gm-Message-State: AO0yUKXbYW2rCqH1zkFavkjNBbQ58MpT9C38ee4BVNs4qM3TbzMuSNvr AneKoFC1UzdJlaXLUd132KrW/gi84OnxLStiBerOYPhi2EOy/tHz/91E0SbJWSp6cKARSN/1JXj aaQSM9yk0uCqfxsejBW4= X-Received: by 2002:aa7:9606:0:b0:593:b0fa:ad95 with SMTP id q6-20020aa79606000000b00593b0faad95mr942989pfg.48.1675095571656; Mon, 30 Jan 2023 08:19:31 -0800 (PST) X-Google-Smtp-Source: AK7set+j5TOl+bWmZTl2QrIqEwxpUZnmcxPOvKeY3B7rrdKEmxeDoLPlXC2Y8aMzgMTR9quXeQLHeTa/xhzpidv5dkU= X-Received: by 2002:aa7:9606:0:b0:593:b0fa:ad95 with SMTP id q6-20020aa79606000000b00593b0faad95mr942986pfg.48.1675095571363; Mon, 30 Jan 2023 08:19:31 -0800 (PST) MIME-Version: 1.0 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> <2954281.hTDNKPQEx9@thomas> In-Reply-To: <2954281.hTDNKPQEx9@thomas> From: David Marchand Date: Mon, 30 Jan 2023 17:19:20 +0100 Message-ID: Subject: Re: [PATCH v10 4/4] eal: deprecation notice for rte thread setname API To: Thomas Monjalon Cc: Tyler Retzlaff , dev@dpdk.org, jerinjacobk@gmail.com, mb@smartsharesystems.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 On Mon, Jan 30, 2023 at 4:47 PM Thomas Monjalon wrote= : > > 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 Yes, I will handle it. > 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. > > > > Signed-off-by: Tyler Retzlaff > > Acked-by: Morten Br=C3=B8rup > > Acked-by: David Marchand > > --- > > +* 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 "sta= ble". And this too. > > > For the series, > Acked-by: Thomas Monjalon Thanks. --=20 David Marchand