From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 925BEA0096 for ; Wed, 5 Jun 2019 09:14:01 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 683D61B95A; Wed, 5 Jun 2019 09:14:01 +0200 (CEST) Received: from mail-vk1-f195.google.com (mail-vk1-f195.google.com [209.85.221.195]) by dpdk.org (Postfix) with ESMTP id 741581B945 for ; Wed, 5 Jun 2019 09:13:58 +0200 (CEST) Received: by mail-vk1-f195.google.com with SMTP id m193so3577264vke.10 for ; Wed, 05 Jun 2019 00:13:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=e7AdoT3ZCn3dq9+EE5HOXNgwFQbv82bGBAXM+udsOZI=; b=pw9IefeZTygBC6RIIBacxbhAPHwdZYXYVQ1okrIin+M7/CrqTCDn8felGDe3TBfmvK X3/1OCP1sfZytPBbQ2IN+LRH5IFQquqSXJLiW+sA3Sp+U6k0Qcy14ASGc3Keu40e+Zt5 mLrtfluHUJHBR18tb9jm+QSrQAt1YEDWa0zn967/O7IupfVPc1r0CFuPiIka5Ykrwi0H BQakPG/Go2XJ02i0iurnFYHAzpqA4j+3bvzaYiryvY0lLCjEw3rWWy2Ikt+lApEV1/pz Can3WkIex96ViibCP9d+gX6taY5X2PHP4RKPMBLaxTYiqjr6x6GBnuLn/GPieU+1e3KB oarg== X-Gm-Message-State: APjAAAUIXtkDrPqisF4fsdOVdWgbzMHMy2Qv3QcFm3XkuqRwgtaldI1Q 2IUUCLvbOO2BDlYOH3XXYv+ZvijTt9XTWQymFcrVzQ== X-Google-Smtp-Source: APXvYqwab2s+JtCOUntkmfWVRBYVPD7QI4oq9T2jCs3D2rT465UlazvPBctk66CthD5Rp2sapk0i4WSVJozf5ZeeQGU= X-Received: by 2002:a1f:1bd0:: with SMTP id b199mr13960330vkb.85.1559718837783; Wed, 05 Jun 2019 00:13:57 -0700 (PDT) MIME-Version: 1.0 References: <20190604163147.105791-1-xiaolong.ye@intel.com> <20190605064910.GA111340@intel.com> In-Reply-To: <20190605064910.GA111340@intel.com> From: David Marchand Date: Wed, 5 Jun 2019 09:13:46 +0200 Message-ID: To: Ye Xiaolong Cc: Ferruh Yigit , dev , dpdk stable Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-stable] [PATCH] eal: correct error log for alarm X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" On Wed, Jun 5, 2019 at 8:58 AM Ye Xiaolong wrote: > On 06/05, David Marchand wrote: > >Hello, > > > >On Tue, Jun 4, 2019 at 6:41 PM Xiaolong Ye wrote: > > > >> Fixes: af75078fece3 ("first public release") > >> Cc: stable@dpdk.org > >> > >> Signed-off-by: Xiaolong Ye > >> --- > >> lib/librte_eal/linux/eal/eal.c | 2 +- > >> 1 file changed, 1 insertion(+), 1 deletion(-) > >> > >> diff --git a/lib/librte_eal/linux/eal/eal.c > >> b/lib/librte_eal/linux/eal/eal.c > >> index 161399619..10e2887ca 100644 > >> --- a/lib/librte_eal/linux/eal/eal.c > >> +++ b/lib/librte_eal/linux/eal/eal.c > >> @@ -1006,7 +1006,7 @@ rte_eal_init(int argc, char **argv) > >> } > >> > >> if (rte_eal_alarm_init() < 0) { > >> - rte_eal_init_alert("Cannot init interrupt-handling > >> thread"); > >> + rte_eal_init_alert("Cannot init alarm"); > >> /* rte_eal_alarm_init sets rte_errno on failure. */ > >> return -1; > >> } > >> -- > >> 2.17.1 > >> > >> > >The same applies to freebsd eal. > > > >lib/librte_eal/freebsd/eal/eal.c: if (rte_eal_alarm_init() < 0) { > >lib/librte_eal/freebsd/eal/eal.c- rte_eal_init_alert("Cannot > >init interrupt-handling thread"); > > Er, yes, do I need to make another separate patch or just add the freebsd > fix > into this patch? > $ git fixline 764bf268 Fixes: 764bf26873b9 ("add FreeBSD support") $ git describe --contains 764bf268 v1.6.0r0~58 Both fixes are old enough to be relevant to the same stable branches (if we want to backport this), so you can add it to this patch yes. -- David Marchand