[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240531181654.GK491852@kernel.org>
Date: Fri, 31 May 2024 19:16:54 +0100
From: Simon Horman <horms@...nel.org>
To: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>
Cc: intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
jacob.e.keller@...el.com, michal.kubiak@...el.com,
maciej.fijalkowski@...el.com, sridhar.samudrala@...el.com,
przemyslaw.kitszel@...el.com, wojciech.drewek@...el.com,
pio.raczynski@...il.com, jiri@...dia.com,
mateusz.polchlopek@...el.com, shayd@...dia.com,
kalesh-anakkur.purayil@...adcom.com
Subject: Re: [iwl-next v3 08/15] ice: make representor code generic
On Tue, May 28, 2024 at 06:38:06AM +0200, Michal Swiatkowski wrote:
> Keep the same flow of port representor creation, but instead of general
> attach function create helpers for specific representor type.
>
> Store function pointer for add and remove representor.
>
> Type of port representor can be also known based on VSI type, but it
> is more clean to have it directly saved in port representor structure.
>
> Add devlink lock for whole port representor creation and destruction.
>
> Reviewed-by: Wojciech Drewek <wojciech.drewek@...el.com>
> Signed-off-by: Michal Swiatkowski <michal.swiatkowski@...ux.intel.com>
Reviewed-by: Simon Horman <horms@...nel.org>
Powered by blists - more mailing lists