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/5] Intel Wired LAN Driver Updates
Date: Thu, 13 Feb 2014 00:00:45 -0800 [thread overview]
Message-ID: <1392278450-27062-1-git-send-email-aaron.f.brown@intel.com> (raw)
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
next reply other threads:[~2014-02-13 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 8:00 Aaron Brown [this message]
2014-02-13 8:00 ` [net-next 1/5] ixgbe: modify behavior on receiving a HW ECC error Aaron Brown
2014-02-13 8:00 ` [net-next 2/5] ixgbe: implement SIOCGHWTSTAMP ioctl Aaron Brown
2014-02-13 20:03 ` Ben Hutchings
2014-02-13 21:46 ` Keller, Jacob E
2014-02-13 8:00 ` [net-next 3/5] ixgbe: don't use magic size number to assign ptp_caps.name Aaron Brown
2014-02-13 8:00 ` [net-next 4/5] ixgbe: Add WoL support for a new device Aaron Brown
2014-02-13 8:00 ` [net-next 5/5] ixgbe: fixup warning regarding max_vfs parameter Aaron Brown
2014-02-13 20:01 ` Ben Hutchings
2014-02-13 20:20 ` 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=1392278450-27062-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