1. 18 11月, 2014 2 次提交
    • M
      i40e: re-enable VFLR interrupt sooner · c5c2f7c3
      Mitch Williams 提交于
      VF interrupt processing takes a looooong time, and it's possible that we
      could lose a VFLR event if it happens while we're processing a VFLR on
      another VF. This would leave the VF in a semi-permanent reset state,
      which would not be cleared until yet another VF experiences a VFLR.
      
      To correct this situation, we enable the VFLR interrupt cause before we
      begin processing any pending resets. This means that any VFLR that
      occurs during reset processing will generate another interrupt and this
      routine will get called again.
      
      This change may cause a spurious interrupt when multiple VFLRs occur
      very close together in time. If this happens, then this routine will be
      called again and it will detect no outstanding VFLR events and do
      nothing. No harm, no foul.
      
      Change-ID: Id0451f3e6e73a2cf6db1668296c71e129b59dc19
      Signed-off-by: NMitch Williams <mitch.a.williams@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      c5c2f7c3
    • S
      i40e: only warn once of PTP nonsupport in 100Mbit speed · e684fa34
      Shannon Nelson 提交于
      Only warn once that PTP is not supported when linked at 100Mbit.
      
      Yes, using a static this way means that this once-only message is not
      port specific, but once only for the life of the driver, regardless of
      the number of ports.  That should be plenty.
      
      Change-ID: Ie6476530056df408452e195ef06afd4f57caa4b2
      Signed-off-by: NShannon Nelson <shannon.nelson@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      e684fa34
  2. 17 11月, 2014 16 次提交
  3. 14 11月, 2014 17 次提交
  4. 13 11月, 2014 5 次提交