From: Greg KH <gregkh@linuxfoundation.org>
To: Manish Chopra <manishc@marvell.com>
Cc: stable@vger.kernel.org, aelior@marvell.com
Subject: Re: [PATCH stable 5.16 1/2] bnx2x: Utilize firmware 7.13.21.0
Date: Thu, 27 Jan 2022 16:23:37 +0100 [thread overview]
Message-ID: <YfK4+TSppmJlXgOh@kroah.com> (raw)
In-Reply-To: <20220125185749.26774-1-manishc@marvell.com>
On Tue, Jan 25, 2022 at 10:57:48AM -0800, Manish Chopra wrote:
> commit b7a49f73059fe6147b6b78e8f674ce0d21237432 upstream
>
> This new firmware addresses few important issues and enhancements
> as mentioned below -
>
> - Support direct invalidation of FP HSI Ver per function ID, required for
> invalidating FP HSI Ver prior to each VF start, as there is no VF start
> - BRB hardware block parity error detection support for the driver
> - Fix the FCOE underrun flow
> - Fix PSOD during FCoE BFS over the NIC ports after preboot driver
> - Maintains backward compatibility
>
> This patch incorporates this new firmware 7.13.21.0 in bnx2x driver.
>
> Signed-off-by: Manish Chopra <manishc@marvell.com>
> Signed-off-by: Prabhakar Kushwaha <pkushwaha@marvell.com>
> Signed-off-by: Alok Prasad <palok@marvell.com>
> Signed-off-by: Ariel Elior <aelior@marvell.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> ---
> drivers/net/ethernet/broadcom/bnx2x/bnx2x.h | 11 +++-
> drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c | 6 +-
> .../net/ethernet/broadcom/bnx2x/bnx2x_fw_defs.h | 2 +
> drivers/net/ethernet/broadcom/bnx2x/bnx2x_hsi.h | 3 +-
> drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c | 75 +++++++++++++++-------
> 5 files changed, 69 insertions(+), 28 deletions(-)
All backports now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-01-27 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 18:57 [PATCH stable 5.16 1/2] bnx2x: Utilize firmware 7.13.21.0 Manish Chopra
2022-01-25 18:57 ` [PATCH stable 5.16 2/2] bnx2x: Invalidate fastpath HSI version for VFs Manish Chopra
2022-01-27 15:23 ` Greg KH [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=YfK4+TSppmJlXgOh@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aelior@marvell.com \
--cc=manishc@marvell.com \
--cc=stable@vger.kernel.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).