netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
	netdev@vger.kernel.org, gospo@redhat.com, bphilips@novell.com
Subject: [net-next-2.6 0/9][pull request] Intel Wired LAN Driver Update
Date: Wed,  4 May 2011 12:30:32 -0700	[thread overview]
Message-ID: <1304537441-2056-1-git-send-email-jeffrey.t.kirsher@intel.com> (raw)

The following series contains updates to e100, igb, igbvf, ixgb and ixgbe.

The following are changes since commit e67f88dd12f610da98ca838822f2c9b4e7c6100e:
  net: dont hold rtnl mutex during netlink dump callbacks
and are available in the git repository at:
  master.kernel.org:/pub/scm/linux/kernel/git/jkirsher/net-next-2.6 master

Carolyn Wyborny (1):
  igb: Add check for invalid size to igb_get_invariants_82575()

Don Skidmore (2):
  ixgbe: fix typo error with software defined pins on 82599
  ixgbe: Cleanup PCIe bus speed info

Emil Tantilov (4):
  e100: fix build warning
  ixgbe: Use function pointer for ixgbe_acquire/release_swfw_sync()
  ixgbe: fix sparse warning
  ixgbe: improve EEPROM read/write operations

Jeff Kirsher (1):
  ixgb: convert to set_phys_id

stephen hemminger (1):
  igbvf: remove bogus phys_id

 drivers/net/e100.c                |    2 +-
 drivers/net/igb/e1000_82575.c     |    8 +
 drivers/net/igbvf/ethtool.c       |    6 -
 drivers/net/ixgb/ixgb.h           |    3 -
 drivers/net/ixgb/ixgb_ethtool.c   |   46 +---
 drivers/net/ixgbe/ixgbe_82598.c   |    1 +
 drivers/net/ixgbe/ixgbe_82599.c   |   38 +++-
 drivers/net/ixgbe/ixgbe_common.c  |  440 +++++++++++++++++++++++++++++--------
 drivers/net/ixgbe/ixgbe_common.h  |    8 +
 drivers/net/ixgbe/ixgbe_ethtool.c |  115 ++++++-----
 drivers/net/ixgbe/ixgbe_main.c    |    7 +-
 drivers/net/ixgbe/ixgbe_phy.c     |   10 +-
 drivers/net/ixgbe/ixgbe_type.h    |    7 +
 drivers/net/ixgbe/ixgbe_x540.c    |   69 ++++++-
 14 files changed, 559 insertions(+), 201 deletions(-)

-- 
1.7.4.4


             reply	other threads:[~2011-05-04 19:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 19:30 Jeff Kirsher [this message]
2011-05-04 19:30 ` [net-next-2.6 1/9] e100: fix build warning Jeff Kirsher
2011-05-04 19:30 ` [net-next-2.6 2/9] ixgb: convert to set_phys_id Jeff Kirsher
2011-05-04 19:30 ` [net-next-2.6 3/9] igb: Add check for invalid size to igb_get_invariants_82575() Jeff Kirsher
2011-05-04 19:30 ` [net-next-2.6 4/9] igbvf: remove bogus phys_id Jeff Kirsher
2011-05-04 19:30 ` [net-next-2.6 5/9] ixgbe: Use function pointer for ixgbe_acquire/release_swfw_sync() Jeff Kirsher
2011-05-04 19:30 ` [net-next-2.6 6/9] ixgbe: fix typo error with software defined pins on 82599 Jeff Kirsher
2011-05-04 19:30 ` [net-next-2.6 7/9] ixgbe: fix sparse warning Jeff Kirsher
2011-05-04 19:30 ` [net-next-2.6 8/9] ixgbe: improve EEPROM read/write operations Jeff Kirsher
2011-05-04 19:30 ` [net-next-2.6 9/9] ixgbe: Cleanup PCIe bus speed info Jeff Kirsher
2011-05-04 20:56 ` [net-next-2.6 0/9][pull request] Intel Wired LAN Driver Update David Miller
2011-05-04 20:59   ` David Miller
2011-05-04 21:14     ` Jeff Kirsher
2011-05-04 21:16       ` 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=1304537441-2056-1-git-send-email-jeffrey.t.kirsher@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=bphilips@novell.com \
    --cc=davem@davemloft.net \
    --cc=gospo@redhat.com \
    --cc=netdev@vger.kernel.org \
    /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).