From: Simon Horman <horms@kernel.org>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
jacob.e.keller@intel.com, michal.kubiak@intel.com,
maciej.fijalkowski@intel.com, sridhar.samudrala@intel.com,
przemyslaw.kitszel@intel.com, wojciech.drewek@intel.com,
pio.raczynski@gmail.com, jiri@nvidia.com,
mateusz.polchlopek@intel.com, shayd@nvidia.com,
kalesh-anakkur.purayil@broadcom.com
Subject: Re: [iwl-next v5 05/15] ice: allocate devlink for subfunction
Date: Fri, 14 Jun 2024 11:55:26 +0100 [thread overview]
Message-ID: <20240614105526.GG8447@kernel.org> (raw)
In-Reply-To: <20240606112503.1939759-6-michal.swiatkowski@linux.intel.com>
On Thu, Jun 06, 2024 at 01:24:53PM +0200, Michal Swiatkowski wrote:
> From: Piotr Raczynski <piotr.raczynski@intel.com>
>
> Make devlink allocation function generic to use it for PF and for SF.
>
> Add function for SF devlink port creation. It will be used in next
> patch.
>
> Create header file for subfunction device. Define subfunction device
> structure there as it is needed for devlink allocation and port
> creation.
>
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Signed-off-by: Piotr Raczynski <piotr.raczynski@intel.com>
> Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Thanks Piotr,
I believe this addresses Jiri's review of v4.
And the minor nit below not withstanding, this looks good to me.
Reviewed-by: Simon Horman <horms@kernel.org>
...
> diff --git a/drivers/net/ethernet/intel/ice/devlink/devlink.c b/drivers/net/ethernet/intel/ice/devlink/devlink.c
...
> @@ -1422,6 +1425,7 @@ static void ice_devlink_free(void *devlink_ptr)
> * Allocate a devlink instance for this device and return the private area as
> * the PF structure. The devlink memory is kept track of through devres by
> * adding an action to remove it when unwinding.
> + *
> */
> struct ice_pf *ice_allocate_pf(struct device *dev)
> {
nit: this hunk seems unrelated to the rest of the patch.
...
next prev parent reply other threads:[~2024-06-14 10:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 11:24 [iwl-next v5 00/15] ice: support devlink subfunction Michal Swiatkowski
2024-06-06 11:24 ` [iwl-next v5 01/15] ice: add new VSI type for subfunctions Michal Swiatkowski
2024-07-23 11:06 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 02/15] ice: export ice ndo_ops functions Michal Swiatkowski
2024-07-23 11:13 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 03/15] ice: add basic devlink subfunctions support Michal Swiatkowski
2024-07-23 11:13 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 04/15] ice: treat subfunction VSI the same as PF VSI Michal Swiatkowski
2024-06-27 11:07 ` Maciej Fijalkowski
2024-06-27 12:31 ` Michal Swiatkowski
2024-07-23 11:14 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 05/15] ice: allocate devlink for subfunction Michal Swiatkowski
2024-06-14 10:55 ` Simon Horman [this message]
2024-07-23 11:15 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 06/15] ice: base subfunction aux driver Michal Swiatkowski
2024-07-23 11:16 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 07/15] ice: implement netdev for subfunction Michal Swiatkowski
2024-06-27 11:13 ` Maciej Fijalkowski
2024-06-27 12:32 ` Michal Swiatkowski
2024-07-23 11:20 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 08/15] ice: make representor code generic Michal Swiatkowski
2024-07-23 11:21 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 09/15] ice: create port representor for SF Michal Swiatkowski
2024-07-23 11:21 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 10/15] ice: don't set target VSI for subfunction Michal Swiatkowski
2024-07-23 11:23 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:24 ` [iwl-next v5 11/15] ice: check if SF is ready in ethtool ops Michal Swiatkowski
2024-07-23 11:24 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:25 ` [iwl-next v5 12/15] ice: implement netdevice ops for SF representor Michal Swiatkowski
2024-06-14 11:02 ` Simon Horman
2024-07-23 11:24 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:25 ` [iwl-next v5 13/15] ice: support subfunction devlink Tx topology Michal Swiatkowski
2024-07-23 11:25 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:25 ` [iwl-next v5 14/15] ice: basic support for VLAN in subfunctions Michal Swiatkowski
2024-07-23 11:25 ` [Intel-wired-lan] " Romanowski, Rafal
2024-06-06 11:25 ` [iwl-next v5 15/15] ice: allow to activate and deactivate subfunction Michal Swiatkowski
2024-07-23 11:26 ` [Intel-wired-lan] " Romanowski, Rafal
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=20240614105526.GG8447@kernel.org \
--to=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jiri@nvidia.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=maciej.fijalkowski@intel.com \
--cc=mateusz.polchlopek@intel.com \
--cc=michal.kubiak@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pio.raczynski@gmail.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=shayd@nvidia.com \
--cc=sridhar.samudrala@intel.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;
as well as URLs for NNTP newsgroup(s).