From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4CC88A04B5 for ; Thu, 29 Oct 2020 11:38:00 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 416EEC960; Thu, 29 Oct 2020 11:37:59 +0100 (CET) Received: from mail-wm1-f66.google.com (mail-wm1-f66.google.com [209.85.128.66]) by dpdk.org (Postfix) with ESMTP id EA1ADC960 for ; Thu, 29 Oct 2020 11:37:56 +0100 (CET) Received: by mail-wm1-f66.google.com with SMTP id c16so1930722wmd.2 for ; Thu, 29 Oct 2020 03:37:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:content-transfer-encoding:user-agent:mime-version; bh=8L88LpoCIJoxGP3YmlhdftP1ttd74IUrhaO75f9wz4E=; b=Dtd3Zq4aTfeNdktjYJupb+ejG2ihorZzQq/VnaT+Qh4/NN7iomLNtzTQbhQY6Cvpdl rQ7Xj4Fa32mYu8Rthdcarfn1gnfv6TDBUCChqQrkp/I6QDYhnYJR4PYEqP8/LMO5SbbG peUMpltpUkI0b0elsow4VscELgFC7/FNB4WzW1iIHhywnJvswwJ1OP+tTC8aRrNk6dOy ZaRtVdPrEylobfGvcuKY8YwaElt3lbQaQySdkULvioJWhSxsySzemMrMeKuyIb39j3av HFFKk4S/7sLR54lTXM6mhmtkzhd9/BZOd0Ecmk7RrUNJHKmeFhvQj3fVRqOEtKAvkVMV 0bXw== X-Gm-Message-State: AOAM533clwNoIdYtCGX0O7yS8AIKhAojLq6p6K4r3odb3NQo0YtKnBnb Icvz/N/sKyoGix6n1CpzRRk= X-Google-Smtp-Source: ABdhPJyAFdwJlX/tNzvlJE1W204r3AXbydzK04C8ReVppOvHJTrjEtc8hi2/CB2zmmq3v0ruDrNurg== X-Received: by 2002:a1c:a90e:: with SMTP id s14mr3759905wme.46.1603967875744; Thu, 29 Oct 2020 03:37:55 -0700 (PDT) Received: from localhost ([88.98.246.218]) by smtp.gmail.com with ESMTPSA id e20sm3739750wme.35.2020.10.29.03.37.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 29 Oct 2020 03:37:55 -0700 (PDT) Message-ID: From: Luca Boccassi To: Kalesh A P , stable@dpdk.org Date: Thu, 29 Oct 2020 10:37:54 +0000 In-Reply-To: <20201029101303.27501-1-kalesh-anakkur.purayil@broadcom.com> References: <20201029101303.27501-1-kalesh-anakkur.purayil@broadcom.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.30.5-1.1 MIME-Version: 1.0 Subject: Re: [dpdk-stable] [PATCH 19.11 1/2] net/bnxt: fix link status during device recovery 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 Thu, 2020-10-29 at 15:43 +0530, Kalesh A P wrote: > From: Kalesh AP >=20 > [ upstream commit 6fcd0de92298f61b8f96ba170db9e81923019626 ] >=20 > Driver should not send the phy_cfg request to bring link down > during reset recovery. If the driver sends the phy_cfg request > in recovery process, then FW needs to re-establish the link which > in turn increases the recovery time based on PHY type and link partners. >=20 > Fixes: df6cd7c1f73a ("net/bnxt: handle reset notify async event from FW") >=20 > Signed-off-by: Kalesh AP > Reviewed-by: Somnath Kotur > Reviewed-by: Ajit Khaparde > --- > drivers/net/bnxt/bnxt_ethdev.c | 6 ++++-- > 1 file changed, 4 insertions(+), 2 deletions(-) Hi, Both of these patches are 100% identical to the ones I pushed yesterday? Was there something unclear in the generated email that made you think the rebase was different that we can fix? https://github.com/bluca/dpdk-stable/commit/d777cb4ecd402ff3f1e73b056f112f4= 78c688948 https://github.com/bluca/dpdk-stable/commit/059f32044f4682c5aedde42e46b7e62= 8550ea480 --=20 Kind regards, Luca Boccassi