Re: [net-next v2 00/14][pull request] 100GbE Intel Wired LAN Driver Updates 2019-11-06

[Jeff Kirsher <jeffrey.t.kirsher@intel.com>]

[-- Attachment #1: Type: text/plain, Size: 2345 bytes --]

On Wed, 2019-11-06 at 11:37 -0800, Jeff Kirsher wrote:
> This series contains updates to ice driver only.
> 
> Jesse implements set_eeprom functionality in ethtool by adding
> functions
> to enable reading of the NVM image.
> 
> Scott adds ethtool -m support so that we can read eeprom data on
> SFP/OSFP
> modules.
> 
> Anirudh updates the return value to properly reflect when SRIOV is
> not
> supported.
> 
> Md Fahad updates the driver to handle a change in the NVM, where the
> boot configuration section was moved to the Preserved Field Area
> (PFA)
> of the NVM.
> 
> Paul resolves an issue when DCBx requests non-contiguous TCs,
> transmit
> hangs could occur, so configure a default traffic class (TC0) in
> these
> cases to prevent traffic hangs.  Adds a print statement to notify the
> user when unsupported modules are inserted.
> 
> Bruce fixes up the driver unload code flow to ensure we do not clear
> the
> interrupt scheme until the reset is complete, otherwise a hardware
> error
> may occur.
> 
> Dave updates the DCB initialization to set is_sw_lldp boolean when
> the
> firmware has been detected to be in an untenable state.  This will
> ensure that the firmware is in a known state.
> 
> Michal saves off the PCI state and I/O BARs address after PCI bus
> reset
> so that after the reset, device registers can be read.  Also adds a
> NULL
> pointer check to prevent a potential kernel panic.
> 
> Mitch resolves an issue where VF's on PF's other than 0 were not
> seeing
> resets by using the per-PF VF ID instead of the absolute VF ID.
> 
> Krzysztof does some code cleanup to remove a unneeded wrapper and
> reduces the code complexity.
> 
> Brett reduces confusion by changing the name of ice_vc_dis_vf() to
> ice_vc_reset_vf() to better describe what the function is actually
> doing.
> 
> v2: dropped patch 3 "ice: Add support for FW recovery mode detection"
>     from the origin al series, while Ani makes changes based on
>     community feedback to implement devlink into the changes.

Sorry for the thrash, I will need to generate a v3 of this series.  I
need to drop patch 1 of the series as well, since these driver changes
will be affected by Ani's work to implement devlink into the driver, as
well as we found a bug with this particular patch.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]