From: Ivan Vecera <ivecera@redhat.com>
To: intel-wired-lan@lists.osuosl.org
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org,
Jacob Keller <jacob.e.keller@intel.com>,
Wojciech Drewek <wojciech.drewek@intel.com>,
Simon Horman <horms@kernel.org>,
mschmidt@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH iwl-next v2 0/5] i40e: Simplify VSI and VEB handling
Date: Thu, 16 Nov 2023 16:01:54 +0100 [thread overview]
Message-ID: <c14fc17e-95a7-47be-86c5-e1c889ea627e@redhat.com> (raw)
In-Reply-To: <20231116144119.78769-1-ivecera@redhat.com>
On 16. 11. 23 15:41, Ivan Vecera wrote:
> The series simplifies handling of VSIs and VEBs by introducing for-each
> iterating macros, 'find' helper functions. Also removes the VEB
> recursion because the VEBs cannot have sub-VEBs according datasheet and
> fixes the support for floating VEBs.
>
> The series content:
> Patch 1 - Uses existing helper function for find FDIR VSI instead of loop
> Patch 2 - Adds and uses macros to iterate VSI and VEB arrays
> Patch 3 - Adds 2 helper functions to find VSIs and VEBs by their SEID
> Patch 4 - Fixes broken support for floating VEBs
> Patch 5 - Removes VEB recursion and simplifies VEB handling
>
> Changelog:
> v1->v2 - small correction in patch 4 description
> - changed helper names in patch 3
>
> Ivan Vecera (5):
> i40e: Use existing helper to find flow director VSI
> i40e: Introduce and use macros for iterating VSIs and VEBs
> i40e: Add helpers to find VSI and VEB by SEID and use them
> i40e: Fix broken support for floating VEBs
> i40e: Remove VEB recursion
>
> drivers/net/ethernet/intel/i40e/i40e.h | 91 ++-
> drivers/net/ethernet/intel/i40e/i40e_dcb_nl.c | 10 +-
> .../net/ethernet/intel/i40e/i40e_debugfs.c | 97 ++-
> drivers/net/ethernet/intel/i40e/i40e_main.c | 563 ++++++++----------
> 4 files changed, 371 insertions(+), 390 deletions(-)
>
Oops, wrong files submitted... Apologies, please forget about this (v2)
series.
Ivan
prev parent reply other threads:[~2023-11-16 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 14:41 [PATCH iwl-next v2 0/5] i40e: Simplify VSI and VEB handling Ivan Vecera
2023-11-16 14:41 ` [PATCH iwl-next v2 1/5] i40e: Use existing helper to find flow director VSI Ivan Vecera
2023-11-16 14:41 ` [PATCH iwl-next v2 2/5] i40e: Introduce and use macros for iterating VSIs and VEBs Ivan Vecera
2023-11-16 14:41 ` [PATCH iwl-next v2 3/5] i40e: Add helpers to find VSI and VEB by SEID and use them Ivan Vecera
2023-11-16 14:41 ` [PATCH iwl-next v2 4/5] i40e: Fix broken support for floating VEBs Ivan Vecera
2023-11-16 14:41 ` [PATCH iwl-next v2 5/5] i40e: Remove VEB recursion Ivan Vecera
2023-11-16 15:01 ` Ivan Vecera [this message]
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=c14fc17e-95a7-47be-86c5-e1c889ea627e@redhat.com \
--to=ivecera@redhat.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wojciech.drewek@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