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
Subject: [net-next 00/11][pull request] Intel Wired LAN Driver Updates 2019-06-17
Date: Mon, 17 Jun 2019 16:33:25 -0700 [thread overview]
Message-ID: <20190617233336.18119-1-jeffrey.t.kirsher@intel.com> (raw)
This series contains updates to the iavf driver only.
Akeem updates the driver to change how VLAN tags are being populated and
programmed into the hardware by starting from the first member of the
list until the number of allowed VLAN tags is exhausted.
Mitch fixed the variable type since the variable counter starts out
negative and climbs to zero, so use a signed integer instead of
unsigned. Also increase the timeout to avoid erroneous errors. Fixed
the driver to be able to handle when the hardware hands us a null
receive descriptor with no data attached, yet is still valid.
Aleksandr fixes the driver to use GFP_ATOMIC when allocating memory in
atomic context.
Avinash updates the driver to fix a calculation error in virtchnl
regarding the valid length.
Jakub does some refactoring of the commands processing the watchdog
state machine to reduce the length and complexity of the function. Also
decalre watchdog task as delayed work and use a dedicated work queue to
service the driver tasks.
Paul updated the iavf_process_aq_command to call the necessary functions
to be able to clear cloud filter bits that need to be cleared.
The following are changes since commit f517f2716c34087ca15a36e9f13dbca8bd2e3ffc:
net: sched: cls_matchall: allow to delete filter
and are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue 40GbE
Akeem G Abodunrin (1):
iavf: Create VLAN tag elements starting from the first element
Aleksandr Loktionov (1):
iavf: Change GFP_KERNEL to GFP_ATOMIC in kzalloc()
Avinash Dayanand (1):
iavf: Fix the math for valid length for ADq enable
Jakub Pawlak (3):
iavf: Move commands processing to the separate function
iavf: Remove timer for work triggering, use delaying work instead
iavf: Refactor init state machine
Jan Sokolowski (1):
iavf: Refactor the watchdog state machine
Mitch Williams (3):
iavf: use signed variable
iavf: wait longer for close to complete
iavf: allow null RX descriptors
Paul Greenwalt (1):
iavf: add call to iavf_[add|del]_cloud_filter
drivers/net/ethernet/intel/iavf/iavf.h | 5 +-
.../net/ethernet/intel/iavf/iavf_ethtool.c | 4 +-
drivers/net/ethernet/intel/iavf/iavf_main.c | 739 ++++++++++--------
drivers/net/ethernet/intel/iavf/iavf_txrx.c | 23 +-
.../net/ethernet/intel/iavf/iavf_virtchnl.c | 4 +-
5 files changed, 440 insertions(+), 335 deletions(-)
--
2.21.0
next reply other threads:[~2019-06-17 23:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 23:33 Jeff Kirsher [this message]
2019-06-17 23:33 ` [net-next 01/11] iavf: Create VLAN tag elements starting from the first element Jeff Kirsher
2019-06-17 23:33 ` [net-next 02/11] iavf: use signed variable Jeff Kirsher
2019-06-17 23:33 ` [net-next 03/11] iavf: wait longer for close to complete Jeff Kirsher
2019-06-17 23:33 ` [net-next 04/11] iavf: Change GFP_KERNEL to GFP_ATOMIC in kzalloc() Jeff Kirsher
2019-06-17 23:33 ` [net-next 05/11] iavf: Fix the math for valid length for ADq enable Jeff Kirsher
2019-06-17 23:33 ` [net-next 06/11] iavf: Move commands processing to the separate function Jeff Kirsher
2019-06-17 23:33 ` [net-next 07/11] iavf: Remove timer for work triggering, use delaying work instead Jeff Kirsher
2019-06-17 23:33 ` [net-next 08/11] iavf: Refactor the watchdog state machine Jeff Kirsher
2019-06-17 23:33 ` [net-next 09/11] iavf: Refactor init " Jeff Kirsher
2019-06-17 23:33 ` [net-next 10/11] iavf: add call to iavf_[add|del]_cloud_filter Jeff Kirsher
2019-06-17 23:33 ` [net-next 11/11] iavf: allow null RX descriptors Jeff Kirsher
2019-06-18 16:44 ` [net-next 00/11][pull request] Intel Wired LAN Driver Updates 2019-06-17 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=20190617233336.18119-1-jeffrey.t.kirsher@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--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