From: Steven Zou <steven.zou@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: jan.sokolowski@intel.com, netdev@vger.kernel.org,
steven.zou@intel.com, andrii.staikov@intel.com,
aleksander.lobakin@intel.com, przemyslaw.kitszel@intel.com,
andriy.shevchenko@linux.intel.com
Subject: [Intel-wired-lan] [PATCH iwl-next 0/2] ice: Introduce switch recipe reusing
Date: Fri, 1 Dec 2023 14:25:00 +0800 [thread overview]
Message-ID: <20231201062502.10099-1-steven.zou@intel.com> (raw)
This patch series firstly fix the bitmap casting issue in getting/mapping
recipe to profile association that is used in both legacy and recipe
reusing mode, then introduce switch recipe reusing feature as new E810
firmware supports the corresponding functionality.
Steven Zou (2):
ice: Refactor FW data type and fix bitmap casting issue
ice: Add switch recipe reusing feature
.../net/ethernet/intel/ice/ice_adminq_cmd.h | 5 +-
drivers/net/ethernet/intel/ice/ice_common.c | 2 +
drivers/net/ethernet/intel/ice/ice_lag.c | 4 +-
drivers/net/ethernet/intel/ice/ice_switch.c | 211 +++++++++++++++---
drivers/net/ethernet/intel/ice/ice_switch.h | 5 +-
drivers/net/ethernet/intel/ice/ice_type.h | 2 +
6 files changed, 197 insertions(+), 32 deletions(-)
base-commit: fce82d0f94e9c1ca953d950ebdb66c6c7f9d53f4
--
2.31.1
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next reply other threads:[~2023-12-01 6:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 6:25 Steven Zou [this message]
2023-12-01 6:25 ` [Intel-wired-lan] [PATCH iwl-next 1/2] ice: Refactor FW data type and fix bitmap casting issue Steven Zou
2023-12-05 19:16 ` Simon Horman
2023-12-01 6:25 ` [Intel-wired-lan] [PATCH iwl-next 2/2] ice: Add switch recipe reusing feature Steven Zou
2023-12-05 19:15 ` Simon Horman
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=20231201062502.10099-1-steven.zou@intel.com \
--to=steven.zou@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=andrii.staikov@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jan.sokolowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.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