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
Subject: [net-next 0/8][pull request] 100GbE Intel Wired LAN Driver Updates 2018-10-01
Date: Mon, 1 Oct 2018 14:14:23 -0700 [thread overview]
Message-ID: <20181001211431.14325-1-jeffrey.t.kirsher@intel.com> (raw)
This series contains updates to ice driver only.
Anirudh provides several changes to "prep" the driver for upcoming
features. Specifically, the functions that are used for PF VSI/netdev
setup will also be used in SR-IOV support and to allow the reuse of
these functions, code needs to move.
Dave provides the only other change in the series, updates the driver to
protect the reset patch in its entirety. This is done by adding the
various bit checks to determine if a reset is scheduled/initiated and
whether it came from the software or firmware.
The following are changes since commit 804fe108fc92e591ddfe9447e7fb4691ed16daee:
openvswitch: Use correct reply values in datapath and vport ops
and are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue 100GbE
Anirudh Venkataramanan (7):
ice: Move common functions out of ice_main.c part 1/7
ice: Move common functions out of ice_main.c part 2/7
ice: Move common functions out of ice_main.c part 3/7
ice: Move common functions out of ice_main.c part 4/7
ice: Move common functions out of ice_main.c part 5/7
ice: Move common functions out of ice_main.c part 6/7
ice: Move common functions out of ice_main.c part 7/7
Dave Ertman (1):
ice: Change pf state behavior to protect reset path
drivers/net/ethernet/intel/ice/Makefile | 1 +
drivers/net/ethernet/intel/ice/ice.h | 2 +-
drivers/net/ethernet/intel/ice/ice_common.c | 61 +
drivers/net/ethernet/intel/ice/ice_common.h | 4 +
drivers/net/ethernet/intel/ice/ice_lib.c | 2379 +++++++++++++++
drivers/net/ethernet/intel/ice/ice_lib.h | 74 +
drivers/net/ethernet/intel/ice/ice_main.c | 2901 ++-----------------
7 files changed, 2773 insertions(+), 2649 deletions(-)
create mode 100644 drivers/net/ethernet/intel/ice/ice_lib.c
create mode 100644 drivers/net/ethernet/intel/ice/ice_lib.h
--
2.17.1
next reply other threads:[~2018-10-02 3:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 21:14 Jeff Kirsher [this message]
2018-10-01 21:14 ` [net-next 1/8] ice: Move common functions out of ice_main.c part 1/7 Jeff Kirsher
2018-10-01 21:14 ` [net-next 2/8] ice: Move common functions out of ice_main.c part 2/7 Jeff Kirsher
2018-10-01 21:14 ` [net-next 3/8] ice: Move common functions out of ice_main.c part 3/7 Jeff Kirsher
2018-10-01 21:14 ` [net-next 4/8] ice: Move common functions out of ice_main.c part 4/7 Jeff Kirsher
2018-10-01 21:14 ` [net-next 5/8] ice: Move common functions out of ice_main.c part 5/7 Jeff Kirsher
2018-10-01 21:14 ` [net-next 6/8] ice: Move common functions out of ice_main.c part 6/7 Jeff Kirsher
2018-10-01 21:14 ` [net-next 7/8] ice: Move common functions out of ice_main.c part 7/7 Jeff Kirsher
2018-10-01 21:14 ` [net-next 8/8] ice: Change pf state behavior to protect reset path Jeff Kirsher
2018-10-01 22:44 ` [net-next 0/8][pull request] 100GbE Intel Wired LAN Driver Updates 2018-10-01 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=20181001211431.14325-1-jeffrey.t.kirsher@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--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