netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Brown <aaron.f.brown@intel.com>
To: davem@davemloft.net
Cc: Aaron Brown <aaron.f.brown@intel.com>,
	netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com
Subject: [net-next 0/6] Intel Wired LAN Driver Updates
Date: Thu, 16 Jan 2014 02:30:04 -0800	[thread overview]
Message-ID: <1389868210-24035-1-git-send-email-aaron.f.brown@intel.com> (raw)

This series contains updates to ixgbe and ixgbevf.

John adds rtnl lock / unlock semantics for ixgbe_reinit_locked()
which was being called without the rtnl lock being held.

Jacob corrects an issue where ixgbevf_qv_disable function does not
set the disabled bit correctly.


>From the community, Wei uses a type of struct for pci driver-specific
data in ixgbevf_suspend()

Don changes the way we store ring arrays in a manner that allows 
support of multiple queues on multiple nodes and creates new ring
initialization functions for work previously done across multiple
functions - making the code closer to ixgbe and hopefully more readable.
He also fixes incorrect fiber eeprom write logic. 

John Fastabend (1):
  ixgbe: reinit_locked() should be called with rtnl_lock

Jacob Keller (1):
  ixgbevf: set the disable state when ixgbevf_qv_disable is called

Wei Yongjun (1):
  ixgbevf: use pci drvdata correctly in ixgbevf_suspend()

Don Skidmore (3):
  ixgbevf: Convert ring storage form pointer to an array to array of
    pointers
  ixgbevf: create function for all of ring init
  ixgbe: Fix incorrect logic for fixed fiber eeprom write

 drivers/net/ethernet/intel/ixgbe/ixgbe_82599.c    |   2 +-
 drivers/net/ethernet/intel/ixgbe/ixgbe_main.c     |   2 +
 drivers/net/ethernet/intel/ixgbevf/defines.h      |  17 +
 drivers/net/ethernet/intel/ixgbevf/ethtool.c      |  30 +-
 drivers/net/ethernet/intel/ixgbevf/ixgbevf.h      |   5 +-
 drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 431 ++++++++++++----------
 6 files changed, 274 insertions(+), 213 deletions(-)

-- 
1.8.5.GIT

             reply	other threads:[~2014-01-16 10:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 10:30 Aaron Brown [this message]
2014-01-16 10:30 ` [net-next 1/6] ixgbe: reinit_locked() should be called with rtnl_lock Aaron Brown
2014-01-16 10:30 ` [net-next 2/6] ixgbevf: set the disable state when ixgbevf_qv_disable is called Aaron Brown
2014-01-16 10:30 ` [net-next 3/6] ixgbevf: use pci drvdata correctly in ixgbevf_suspend() Aaron Brown
2014-01-16 10:30 ` [net-next 4/6] ixgbevf: Convert ring storage form pointer to an array to array of pointers Aaron Brown
2014-01-16 10:30 ` [net-next 5/6] ixgbevf: create function for all of ring init Aaron Brown
2014-01-16 10:30 ` [net-next 6/6] ixgbe: Fix incorrect logic for fixed fiber eeprom write Aaron Brown
2014-01-16 23:35 ` [net-next 0/6] Intel Wired LAN Driver Updates David Miller
  -- strict thread matches above, loose matches on Subject: below --
2014-02-28  4:32 Aaron Brown
2014-02-28  5:41 ` David Miller
2014-02-26  1:58 Aaron Brown
2014-01-14  8:49 Aaron Brown
2014-01-15  2:56 ` 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=1389868210-24035-1-git-send-email-aaron.f.brown@intel.com \
    --to=aaron.f.brown@intel.com \
    --cc=davem@davemloft.net \
    --cc=gospo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=sassmann@redhat.com \
    /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).