From: Stefano Brivio <sbrivio@redhat.com>
To: davem@davemloft.net
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com
Subject: Re: [net 0/2][pull request] Intel Wired LAN Driver Updates 2017-09-05
Date: Wed, 6 Sep 2017 12:55:51 +0200 [thread overview]
Message-ID: <20170906125551.057e71e0@elisabeth> (raw)
In-Reply-To: <20170906010418.39007-1-jeffrey.t.kirsher@intel.com>
On Tue, 5 Sep 2017 18:04:16 -0700
Jeff Kirsher <jeffrey.t.kirsher@intel.com> wrote:
> This series contains fixes for i40e only.
>
> These two patches fix an issue where our nvmupdate tool does not work on RHEL 7.4
> and newer kernels, in fact, the use of the nvmupdate tool on newer kernels can
> cause the cards to be non-functional unless these patches are applied.
>
> Anjali reworks the locking around accessing the NVM so that NVM acquire timeouts
> do not occur which was causing the failed firmware updates.
>
> Jake correctly updates the wb_desc when reading the NVM through the AdminQ.
>
> The following are changes since commit 6d9c153a0b84392406bc77600aa7d3ea365de041:
> net: dsa: loop: Do not unregister invalid fixed PHY
> and are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/net-queue 40GbE
>
> Anjali Singhai Jain (1):
> i40e: avoid NVM acquire deadlock during NVM update
>
> Jacob Keller (1):
> i40e: point wb_desc at the nvm_wb_desc during i40e_read_nvm_aq
I think this should go to -stable too (4.12+), as cards completely
stop working after a firmware upgrade.
prev parent reply other threads:[~2017-09-06 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 1:04 [net 0/2][pull request] Intel Wired LAN Driver Updates 2017-09-05 Jeff Kirsher
2017-09-06 1:04 ` [net 1/2] i40e: avoid NVM acquire deadlock during NVM update Jeff Kirsher
2017-09-06 1:04 ` [net 2/2] i40e: point wb_desc at the nvm_wb_desc during i40e_read_nvm_aq Jeff Kirsher
2017-09-06 3:03 ` [net 0/2][pull request] Intel Wired LAN Driver Updates 2017-09-05 David Miller
2017-09-06 10:55 ` Stefano Brivio [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=20170906125551.057e71e0@elisabeth \
--to=sbrivio@redhat.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jogreene@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.com \
/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).