From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: davem@davemloft.net, kuba@kernel.org
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com
Subject: [net-next 0/8][pull request] 100GbE Intel Wired LAN Driver Updates 2020-10-07
Date: Wed, 7 Oct 2020 10:54:39 -0700 [thread overview]
Message-ID: <20201007175447.647867-1-anthony.l.nguyen@intel.com> (raw)
This series contains updates to ice driver only.
Andy Shevchenko changes usage to %*phD format to print small buffer as hex
string.
Bruce removes repeated words reported by checkpatch.
Ani changes ice_info_get_dsn() to return void as it always returns
success.
Jake adds devlink reporting of fw.app.bundle_id. Moves devlink_port
structure to ice_vsi to resolve issues with cleanup. Adds additional
debug info for firmware updates.
Bixuan Cui resolves -Wpointer-to-int-cast warnings.
Dan adds additional packet type masks and checks to prevent overwriting
existing Flow Director rules.
The following are changes since commit 9faebeb2d80065926dfbc09cb73b1bb7779a89cd:
Merge branch 'ethtool-allow-dumping-policies-to-user-space'
and are available in the git repository at:
https://github.com/anguy11/next-queue.git 100GbE
Andy Shevchenko (1):
ice: devlink: use %*phD to print small buffer
Anirudh Venkataramanan (1):
ice: Change ice_info_get_dsn to be void
Bixuan Cui (1):
ice: Fix pointer cast warnings
Bruce Allan (1):
ice: remove repeated words
Dan Nowlin (1):
ice: fix adding IP4 IP6 Flow Director rules
Jacob Keller (3):
ice: add the DDP Track ID to devlink info
ice: refactor devlink_port to be per-VSI
ice: add additional debug logging for firmware update
Documentation/networking/devlink/ice.rst | 5 ++
drivers/net/ethernet/intel/ice/ice.h | 7 +-
drivers/net/ethernet/intel/ice/ice_devlink.c | 78 +++++++++++--------
drivers/net/ethernet/intel/ice/ice_devlink.h | 4 +-
.../net/ethernet/intel/ice/ice_flex_pipe.c | 2 +-
drivers/net/ethernet/intel/ice/ice_flow.c | 66 +++++++++++++++-
drivers/net/ethernet/intel/ice/ice_flow.h | 4 +-
.../net/ethernet/intel/ice/ice_fw_update.c | 28 +++++--
drivers/net/ethernet/intel/ice/ice_lib.c | 5 +-
drivers/net/ethernet/intel/ice/ice_main.c | 19 +++--
.../net/ethernet/intel/ice/ice_virtchnl_pf.c | 2 +-
11 files changed, 162 insertions(+), 58 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-07 19:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 17:54 Tony Nguyen [this message]
2020-10-07 17:54 ` [net-next 1/8] ice: devlink: use %*phD to print small buffer Tony Nguyen
2020-10-07 17:54 ` [net-next 2/8] ice: remove repeated words Tony Nguyen
2020-10-07 17:54 ` [net-next 3/8] ice: Change ice_info_get_dsn to be void Tony Nguyen
2020-10-07 17:54 ` [net-next 4/8] ice: add the DDP Track ID to devlink info Tony Nguyen
2020-10-07 17:54 ` [net-next 5/8] ice: refactor devlink_port to be per-VSI Tony Nguyen
2020-10-07 17:54 ` [net-next 6/8] ice: add additional debug logging for firmware update Tony Nguyen
2020-10-07 17:54 ` [net-next 7/8] ice: Fix pointer cast warnings Tony Nguyen
2020-10-07 17:54 ` [net-next 8/8] ice: fix adding IP4 IP6 Flow Director rules Tony Nguyen
2020-10-07 20:39 ` [net-next 0/8][pull request] 100GbE Intel Wired LAN Driver Updates 2020-10-07 Jakub Kicinski
2020-10-09 20:23 ` Jakub Kicinski
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=20201007175447.647867-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=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).