From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
netdev@vger.kernel.org, sassmann@redhat.com
Subject: [PATCH net 0/2][pull request] Intel Wired LAN Driver Updates 2022-04-20
Date: Wed, 20 Apr 2022 10:26:22 -0700 [thread overview]
Message-ID: <20220420172624.931237-1-anthony.l.nguyen@intel.com> (raw)
This series contains updates to iavf and i40e drivers.
Michal adds a check for down states before changing ring parameters to
avoid possible corruption for iavf.
Xiaomeng Tong prevents possible use of incorrect 'ch' variable by
introducing an interim iterator variable for i40e.
The following are changes since commit 5e6242151d7f17b056a82ca7b860c4ec8eaa7589:
selftests: mlxsw: vxlan_flooding_ipv6: Prevent flooding of unwanted packets
and are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue 40GbE
Michal Maloszewski (1):
iavf: Fix error when changing ring parameters on ice PF
Xiaomeng Tong (1):
i40e: i40e_main: fix a missing check on list iterator
drivers/net/ethernet/intel/i40e/i40e_main.c | 27 ++++++++++---------
.../net/ethernet/intel/iavf/iavf_ethtool.c | 5 ++++
2 files changed, 19 insertions(+), 13 deletions(-)
--
2.31.1
next reply other threads:[~2022-04-20 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 17:26 Tony Nguyen [this message]
2022-04-20 17:26 ` [PATCH net 1/2] iavf: Fix error when changing ring parameters on ice PF Tony Nguyen
2022-04-22 22:47 ` Jakub Kicinski
2022-04-28 18:10 ` Maloszewski, Michal
2022-04-28 18:28 ` Jakub Kicinski
2022-04-29 13:14 ` Maloszewski, Michal
2022-04-29 17:57 ` Jakub Kicinski
2022-05-09 15:25 ` Maloszewski, Michal
2022-04-20 17:26 ` [PATCH net 2/2] i40e: i40e_main: fix a missing check on list iterator Tony Nguyen
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=20220420172624.931237-1-anthony.l.nguyen@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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).