netdev - [net-next 0/5] Intel Wired LAN Driver Updates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1392278450-27062-1-git-send-email-aaron.f.brown@intel.com>
Date:	Thu, 13 Feb 2014 00:00:45 -0800
From:	Aaron Brown <aaron.f.brown@...el.com>
To:	davem@...emloft.net
Cc:	Aaron Brown <aaron.f.brown@...el.com>, netdev@...r.kernel.org,
	gospo@...hat.com, sassmann@...hat.com
Subject: [net-next 0/5] Intel Wired LAN Driver Updates

This series contains updates to the ixgbe driver.

Don makes recovery from a HW ECC error just schedule a reset as it turns
out the previous behaviour of forcing the user to reload is not necessary.

Jacob adds support for the new SIOCGHWTSTAMP ioctl, removes a magic number
from the ptp_caps.name assignment and makes a warning message much more
useful.

Mark add WOL support for a new part.

Don Skidmore (1):
  ixgbe: modify behavior on receiving a HW ECC error.

Jacob Keller (3):
  ixgbe: implement SIOCGHWTSTAMP ioctl
  ixgbe: don't use magic size number to assign ptp_caps.name
  ixgbe: fixup warning regarding max_vfs parameter

Mark Rustad (1):
  ixgbe: Add WoL support for a new device

 drivers/net/ethernet/intel/ixgbe/ixgbe.h      |  5 ++--
 drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 37 +++++++++++++++++------
 drivers/net/ethernet/intel/ixgbe/ixgbe_ptp.c  | 43 +++++++++++++++++----------
 drivers/net/ethernet/intel/ixgbe/ixgbe_type.h |  1 +
 4 files changed, 60 insertions(+), 26 deletions(-)

-- 
1.8.5.GIT

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html