From: Luca Boccassi <bluca@debian.org>
To: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 19.11 1/2] net/bnxt: fix link status during device recovery
Date: Thu, 29 Oct 2020 10:37:54 +0000 [thread overview]
Message-ID: <ac2c71b8cee937ae0729ad5ea3193fcdc0bc392d.camel@debian.org> (raw)
In-Reply-To: <20201029101303.27501-1-kalesh-anakkur.purayil@broadcom.com>
On Thu, 2020-10-29 at 15:43 +0530, Kalesh A P wrote:
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>
> [ upstream commit 6fcd0de92298f61b8f96ba170db9e81923019626 ]
>
> 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.
>
> Fixes: df6cd7c1f73a ("net/bnxt: handle reset notify async event from FW")
>
> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> ---
> 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/d777cb4ecd402ff3f1e73b056f112f478c688948
https://github.com/bluca/dpdk-stable/commit/059f32044f4682c5aedde42e46b7e628550ea480
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2020-10-29 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 10:13 Kalesh A P
2020-10-29 10:13 ` [dpdk-stable] [PATCH 19.11 2/2] net/bnxt: fix link update Kalesh A P
2020-10-29 10:37 ` Luca Boccassi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ac2c71b8cee937ae0729ad5ea3193fcdc0bc392d.camel@debian.org \
--to=bluca@debian.org \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=stable@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).