netdev - [net v2 0/4][pull request] 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 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]

Date:	Fri,  4 May 2012 04:05:00 -0700
From:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
To:	davem@...emloft.net
Cc:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>, netdev@...r.kernel.org,
	gospo@...hat.com, sassmann@...hat.com
Subject: [net v2 0/4][pull request] Intel Wired LAN Driver Updates

This series of patches contains fixes for ixgbe, igb and e1000.

v2: Added e1000 patch to fix sparse warnings and igb/ixgbe to
    correct an issue of calling function to reset Tx queue in
    init path.

The following are changes since commit 5a8887d39e1ba5ee2d4ccb94b14d6f2dce5ddfca:
  sungem: Fix WakeOnLan
and are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/net master`

Andrei Emeltchenko (1):
  e1000: Silence sparse warnings by correcting type

Don Skidmore (1):
  ixgbe: fix race condition with shutdown

John Fastabend (2):
  ixgbe: dcb: BIT_APP_UPCHG not set by ixgbe_copy_dcb_cfg()
  igb, ixgbe: netdev_tx_reset_queue incorrectly called from tx init
    path

 drivers/net/ethernet/intel/e1000/e1000_main.c    |    4 +-
 drivers/net/ethernet/intel/igb/igb_main.c        |    4 +-
 drivers/net/ethernet/intel/ixgbe/ixgbe.h         |    3 --
 drivers/net/ethernet/intel/ixgbe/ixgbe_dcb_nl.c  |   43 ++++++++++------------
 drivers/net/ethernet/intel/ixgbe/ixgbe_ethtool.c |    2 +
 drivers/net/ethernet/intel/ixgbe/ixgbe_main.c    |   10 +++--
 6 files changed, 32 insertions(+), 34 deletions(-)

-- 
1.7.7.6

--
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