From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com, john.ronciak@intel.com
Subject: Re: [net-next 0/8][pull request] Intel Wired LAN Driver Updates 2015-09-17
Date: Fri, 18 Sep 2015 09:58:04 -0700 [thread overview]
Message-ID: <1442595484.2873.5.camel@intel.com> (raw)
In-Reply-To: <1442535480-65222-1-git-send-email-jeffrey.t.kirsher@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
On Thu, 2015-09-17 at 17:17 -0700, Jeff Kirsher wrote:
> This series contains updates to i40e and i40evf.
>
> Shannon provides updates to i40e and i40evf to resolve an issue with
> the
> nvmupdate utility. First renames a variable name to reduce confusion
> and
> to differentiate it from the actual user variable. Then added the
> ability
> to save the admin queue write back descriptor if a caller supplies a
> buffer for it to be saved into. Added a new GetStatus command so
> that
> the NVM update tool can query the current status instead of doing
> fake
> write requests to probe for readiness. Added wait states to the NVM
> update state machine to signify when waiting for an update operation
> to
> finish, whether we are in the middle of a set of write operations, or
> we
> are now idle but waiting. Then added a facility to run admin queue
> commands through the NVM update utility in order to allow the update
> tools to interact with the firmware and do special commands needed
> for
> updates and configuration changes. Also added a facility to recover
> the
> result of a previously run admin queue command.
To add, this series adds necessary capability to the driver to extend
the nvmupdate utility to be compatible with the latest released
adapters. Without it, the already released nvmupdate utilities won't
work.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-09-18 16:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 0:17 [net-next 0/8][pull request] Intel Wired LAN Driver Updates 2015-09-17 Jeff Kirsher
2015-09-18 0:17 ` [net-next 1/8] i40e: rename variable to prevent clash of understanding Jeff Kirsher
2015-09-18 0:17 ` [net-next 2/8] i40e/i40evf: save aq writeback for future inspection Jeff Kirsher
2015-09-18 0:17 ` [net-next 3/8] i40e/i40evf: add handling of writeback descriptor Jeff Kirsher
2015-09-18 0:17 ` [net-next 4/8] i40e/i40evf: add GetStatus command for nvmupdate Jeff Kirsher
2015-09-18 0:17 ` [net-next 5/8] i40e/i40evf: add wait states to NVM state machine Jeff Kirsher
2015-09-18 0:17 ` [net-next 6/8] i40e/i40evf: add exec_aq command to nvmupdate utility Jeff Kirsher
2015-09-18 0:17 ` [net-next 7/8] i40e/i40evf: add get AQ result " Jeff Kirsher
2015-09-18 0:18 ` [net-next 8/8] i40e/i40evf: Bump i40e to 1.3.21 and i40evf to 1.3.13 Jeff Kirsher
2015-09-18 1:00 ` [net-next 0/8][pull request] Intel Wired LAN Driver Updates 2015-09-17 Jeff Kirsher
2015-09-18 16:58 ` Jeff Kirsher [this message]
2015-09-21 5:27 ` David Miller
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=1442595484.2873.5.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=jogreene@redhat.com \
--cc=john.ronciak@intel.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).