From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com, guru.anbalagane@oracle.com
Subject: [net-next 0/4][pull request] 10GbE Intel Wired LAN Driver Updates 2016-08-18
Date: Thu, 18 Aug 2016 23:03:32 -0700 [thread overview]
Message-ID: <1471586616-64728-1-git-send-email-jeffrey.t.kirsher@intel.com> (raw)
This series contains updates to ixgbe and ixgbevf.
Emil cleans up confusing amongst the users by making an error message
into a debug message, since the TXDCTL.ENABLE (and comparable
VFTXDCTL.ENABLE for ixgbevf) bit is set only when the
transmit queue is actually enabled, which may not happen during the
configure phase eve if we waited for it. Converts to using netdev_dbg()
macro instead of our home brewed macro for ixgbevf. Converted the
service task to use atomic bitwise operations when setting and checking
reset requests to reduce the possibility of race conditions.
The following are changes since commit e951f145d1724769546efe2e04f6cb2b7037d7ea:
Merge branch 'tipc-next'
and are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue 10GbE
Emil Tantilov (4):
ixgbe: only check Tx queue enablement when debugging
ixgbevf: change hw_dbg to use netdev_dbg
ixgbevf: only check Tx queue enablement when debugging
ixgbe: use atomic bitwise operations when handling reset requests
drivers/net/ethernet/intel/ixgbe/ixgbe.h | 2 +-
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 18 ++++++++----------
drivers/net/ethernet/intel/ixgbevf/ixgbevf.h | 11 ++++-------
drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 3 ++-
4 files changed, 15 insertions(+), 19 deletions(-)
--
2.7.4
next reply other threads:[~2016-08-19 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 6:03 Jeff Kirsher [this message]
2016-08-19 6:03 ` [net-next 1/4] ixgbe: only check Tx queue enablement when debugging Jeff Kirsher
2016-08-19 6:03 ` [net-next 2/4] ixgbevf: change hw_dbg to use netdev_dbg Jeff Kirsher
2016-08-19 6:03 ` [net-next 3/4] ixgbevf: only check Tx queue enablement when debugging Jeff Kirsher
2016-08-19 6:03 ` [net-next 4/4] ixgbe: use atomic bitwise operations when handling reset requests Jeff Kirsher
2016-08-20 0:19 ` [net-next 0/4][pull request] 10GbE Intel Wired LAN Driver Updates 2016-08-18 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=1471586616-64728-1-git-send-email-jeffrey.t.kirsher@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=guru.anbalagane@oracle.com \
--cc=jogreene@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--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).